Migrating data to disk without interrupting running operations

ABSTRACT

Systems and methods for migrating stored backup data between disks (e.g., from an existing disk to another disk), such as a new or different disk in a magnetic storage library, without interrupting or otherwise affecting secondary copy operations (e.g., operations currently writing data to the storage library) utilizing the magnetic storage library, are described. In some embodiments, the systems and methods mark one or more mount paths as full when a running secondary copy operation associated with the mount path has completed a job (regardless of the actual current capacity or intended use of the mount path), and migrate each of the one or more data to a second disk of the data storage library when the mount path associated with the data is marked as full.

INCORPORATION BY REFERENCE TO ANY PRIORITY APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/101,392, filed on Aug. 10, 2018, and titled “MIGRATING DATA TO DISKWITHOUT INTERRUPTING RUNNING OPERATIONS,” which is a continuation ofU.S. patent application Ser. No. 14/843,075, filed on Sep. 2, 2015, andtitled “MIGRATING DATA TO DISK WITHOUT INTERRUPTING RUNNING BACKUPOPERATIONS,” (U.S. Pat. No. 10,101,913), which is hereby incorporated byreference in its entirety. Any and all applications, if any, for which aforeign or domestic priority claim is identified in the Application DataSheet of the present application are hereby incorporated by referenceunder 37 CFR 1.57.

BACKGROUND

Businesses worldwide recognize the commercial value of their data andseek reliable, cost-effective ways to protect the information stored ontheir computer networks while minimizing impact on productivity.Protecting information is often part of a routine process that isperformed within an organization. A company might back up criticalcomputing systems such as databases, file servers, web servers, and soon as part of a daily, weekly, or monthly maintenance schedule. Thecompany may similarly protect computing systems used by each of itsemployees, such as those used by an accounting department, marketingdepartment, engineering department, and so forth.

Given the rapidly expanding volume of data under management, companiesalso continue to seek innovative techniques for managing data growth, inaddition to protecting data. For instance, companies often implementmigration techniques for moving data to lower cost storage over time anddata reduction techniques for reducing redundant data, pruning lowerpriority data, etc. Enterprises also increasingly view their stored dataas a valuable asset. Along these lines, customers are looking forsolutions that not only protect and manage, but also leverage theirdata. For instance, solutions providing data analysis capabilities,information management, improved data presentation and access features,and the like, are in increasing demand.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is a block diagram illustrating an exemplary informationmanagement system.

FIG. 1B is a detailed view of a primary storage device, a secondarystorage device, and some examples of primary data and secondary copydata.

FIG. 1C is a block diagram of an exemplary information management systemincluding a storage manager, one or more data agents, and one or moremedia agents.

FIG. 1D is a block diagram illustrating a scalable informationmanagement system.

FIG. 1E illustrates certain secondary copy operations according to anexemplary storage policy.

FIGS. 1F-1H are block diagrams illustrating suitable data structuresthat may be employed by the information management system.

FIG. 2 is a block diagram illustrating devices for storing data from acomputing device to magnetic disk storage.

FIG. 3 is a block diagram illustrating some salient portions of a diskmigration system, according to an illustrative embodiment of the presentinvention.

FIG. 4 depicts some salient operations of a method for migrating datafrom an existing magnetic disk to a new magnetic disk within magneticstorage, according to an illustrative embodiment of the presentinvention.

FIG. 5 depicts some salient operations of a method for transferring datato magnetic storage during a magnetic disk migration, according to anillustrative embodiment of the present invention.

FIGS. 6A-6C are block diagrams illustrating magnetic disk migration inmagnetic disk storage.

DETAILED DESCRIPTION

A magnetic library is a virtual library associated with one or moremount paths. A magnetic library does not represent a specific hardwareentity; instead it provides a schema or list of mount paths throughwhich data is sent, copied, transferred, or otherwise streamed tomagnetic media within secondary storage. Magnetic media may includeindividual hard magnetic disks or RAID arrays, which are logicallydivided into partitions, that include some or all of the total magneticdisk storage space available to store data volumes. A partition of amagnetic disk may be associated with a file system path, called a mountpath, through which data is written to the magnetic disk and read fromthe magnetic disk. The magnetic library may be configured by assigningone or more mount paths to the library, and the storage capacity,therefore, of a magnetic library, is determined by the total storagespace provided by the assigned mount paths.

At times, a customer of an information management system may want toreplace existing magnetic disks storing data volumes (e.g., backup orother secondary copies) with new magnetic disks. However, problems arisewhen attempting to migrate the data volumes from the existing disks tothe new disks, because secondary copy operations (e.g., backupoperations) should not utilize a mount path when the mount path (e.g.,the data volume contained by the mount path) is being transferred froman existing disk associated with the mount path to the new disk, as datainconsistencies may arise due to possible changes to the data before andafter the data volume is transferred, among other drawbacks.

For example, a data volume, which may be a sub-division or portion of amount path, may contain many terabytes of data (e.g., multiple hours ofdata to transfer to secondary copies). Preventing use of an associatedmount path while the many terabytes are transferred or migrated from onedisk to another may cause significant delays to running data storageoperations, as the associated mount path will be inaccessible until thedata volume is copied to the new disk. Therefore, techniques thatmigrate data between existing and new magnetic disks within magneticstorage (e.g., within a magnetic storage library) without interruptingrunning secondary copy operations using the magnetic storage wouldprovide various benefits to an information management system.

Systems and methods for migrating stored backup data between magneticdisks (e.g., from an existing magnetic disk to another disk), such as anew or different magnetic disk in a magnetic storage library, withoutinterrupting or otherwise affecting secondary copy operations (e.g.,operations currently writing data to the storage library) utilizing themagnetic storage library, are described. For example, the systems andmethods may refresh the mount paths represented by a virtual magneticlibrary by, for all non-active (e.g. full) data volumes, migrating, at afirst time, the non-active data volumes to the new magnetic disk, andfor all active (open) data volumes associated with the currently runningsecondary copy operations, marking each data volume as non-active when arunning secondary copy operation associated with the mount path and datavolume has completed a job and migrating, at a second time later thanthe first time, data volumes associated with the mount path marked asnon-active to the new magnetic disk, and for all data volumes migratedto the new magnetic disk, marking each data volume as resident on thenew magnetic disk.

Furthermore, the systems and methods may maintain currently runningsecondary copy operations by creating one or more temporary mount pathson the new magnetic disk for all the active data volumes associated withthe currently running secondary copy operations, sending all jobsperformed by the running secondary copy operations to the createdtemporary mount paths during migration of data volumes associated withmount paths marked as non-active to the new magnetic disk, and when thedata volumes marked as non-active are marked as resident on the newmagnetic disk, returning all jobs performed by the running secondarycopy operations to the mount paths marked as resident on the newmagnetic disk.

While aspects of the invention are generally described below asmigrating data to a new magnetic disk library, migrating to other datastorage media is possible, including, e.g., transferring data to opticaldisk(s).

Examples of such systems and methods are described in further detailherein, in reference to FIGS. 2-5 and the section entitled EXAMPLES OFMIGRATING DATA BETWEEN MAGNETIC DISKS IN MAGNETIC STORAGE disclosedherein. Components and functionality utilized when migrating storedsecondary data to other storage media without interrupting secondarycopy operations may be configured and/or incorporated into informationmanagement systems such as those described herein in FIGS. 1A-1H.

Information Management System Overview

With the increasing importance of protecting and leveraging data,organizations simply cannot risk losing critical data. Moreover, runawaydata growth and other modern realities make protecting and managing dataincreasingly difficult. There is therefore a need for efficient,powerful, and user-friendly solutions for protecting and managing data.Depending on the size of the organization, there may be many dataproduction sources which are under the purview of tens, hundreds, oreven thousands of individuals. In the past, individuals were sometimesresponsible for managing and protecting their own data, and a patchworkof hardware and software point solutions may have been used in any givenorganization. These solutions were often provided by different vendorsand had limited or no interoperability. Certain embodiments describedherein address these and other shortcomings of prior approaches byimplementing scalable, unified, organization-wide informationmanagement, including data storage management.

FIG. 1A shows one such information management system 100 (or “system100”), which generally includes combinations of hardware and softwareconfigured to protect and manage data and metadata that are generatedand used by computing devices in system 100. System 100 may be referredto in some embodiments as a “storage management system” and theoperations it performs may be referred to as “information managementoperations” or “storage operations” in some circumstances. Theorganization that employs system 100 may be a corporation or otherbusiness entity, non-profit organization, educational institution,household, governmental agency, or the like.

Generally, the systems and associated components described herein may becompatible with and/or provide some or all of the functionality of thesystems and corresponding components described in one or more of thefollowing U.S. patents and patent application publications assigned toCommvault Systems, Inc., each of which is hereby incorporated byreference in its entirety herein:

U.S. Pat. No. 7,035,880, entitled “Modular Backup and Retrieval SystemUsed in Conjunction With a Storage Area Network”;

U.S. Pat. No. 7,107,298, entitled “System And Method For ArchivingObjects In An Information Store”;

U.S. Pat. No. 7,246,207, entitled “System and Method for DynamicallyPerforming Storage Operations in a Computer Network”;

U.S. Pat. No. 7,315,923, entitled “System And Method For Combining DataStreams In Pipelined Storage Operations In A Storage Network”;

U.S. Pat. No. 7,343,453, entitled “Hierarchical Systems and Methods forProviding a Unified View of Storage Information”;

U.S. Pat. No. 7,395,282, entitled “Hierarchical Backup and RetrievalSystem”;

U.S. Pat. No. 7,529,782, entitled “System and Methods for Performing aSnapshot and for Restoring Data”;

U.S. Pat. No. 7,617,262, entitled “System and Methods for MonitoringApplication Data in a Data Replication System”;

U.S. Pat. No. 7,734,669, entitled “Managing Copies Of Data”;

U.S. Pat. No. 7,747,579, entitled “Metabase for Facilitating DataClassification”;

U.S. Pat. No. 8,156,086, entitled “Systems And Methods For Stored DataVerification”;

U.S. Pat. No. 8,170,995, entitled “Method and System for OfflineIndexing of Content and Classifying Stored Data”;

U.S. Pat. No. 8,230,195, entitled “System And Method For PerformingAuxiliary Storage Operations”;

U.S. Pat. No. 8,285,681, entitled “Data Object Store and Server for aCloud Storage Environment, Including Data Deduplication and DataManagement Across Multiple Cloud Storage Sites”;

U.S. Pat. No. 8,307,177, entitled “Systems And Methods For Management OfVirtualization Data”;

U.S. Pat. No. 8,364,652, entitled “Content-Aligned, Block-BasedDeduplication”;

U.S. Pat. No. 8,578,120, entitled “Block-Level Single Instancing”;

U.S. Pat. Pub. No. 2006/0224846, entitled “System and Method to SupportSingle Instance Storage Operations”;

U.S. Pat. Pub. No. 2009/0319534, entitled “Application-Aware and RemoteSingle Instance Data Management”;

U.S. Pat. Pub. No. 2012/0150818, entitled “Client-Side Repository in aNetworked Deduplicated Storage System”; and

U.S. Pat. Pub. No. 2012/0150826, entitled “Distributed DeduplicatedStorage System”.

Information management system 100 can include a variety of computingdevices and computing technologies. For instance, system 100 can includeone or more client computing devices 102 and secondary storage computingdevices 106, as well as storage manager 140 or a host computing devicefor it. Computing devices can include, without limitation, one or more:workstations, personal computers, desktop computers, or other types ofgenerally fixed computing systems such as mainframe computers, servers,and minicomputers. Other computing devices can include mobile orportable computing devices, such as one or more laptops, tabletcomputers, personal data assistants, mobile phones (such assmartphones), and other mobile or portable computing devices such asembedded computers, set top boxes, vehicle-mounted devices, wearablecomputers, etc. Servers can include mail servers, file servers, databaseservers, and web servers. Computing devices may comprise one or moreprocessors (e.g., CPU and/or single-core or multi-core processors), aswell as non-transitory computer-readable memory (e.g., random-accessmemory (RAM)) for storing computer programs to be executed by the one ormore processors. Other computer-readable memory for mass storage of datamay be packaged/configured with the computing device (e.g., an internalhard disk) and/or may be external and accessible by the computing device(e.g., network-attached storage).

In some cases, a computing device includes cloud computing resources,which may be virtual machines. For instance, one or more virtualmachines may be provided to the organization by a third-party cloudservice vendor. In some embodiments, computing devices can include oneor more virtual machine(s) running on a physical host computing device(or “host machine”) operated by the organization. As one example, theorganization may use one virtual machine as a database server andanother virtual machine as a mail server, both virtual machinesoperating on the same host machine.

A virtual machine includes an operating system and associated virtualresources, and is hosted simultaneously with another operating system ona physical host computer (or host machine). A hypervisor (typicallysoftware, and also known in the art as a virtual machine monitor or avirtual machine manager or “VMM”) sits between the virtual machine andthe hardware of the physical host machine. Examples of hypervisors asvirtualization software include ESX Server, by VMware, Inc. of PaloAlto, Calif.; Microsoft Virtual Server and Microsoft Windows ServerHyper-V, both by Microsoft Corporation of Redmond, Wash.; and Sun xVM byOracle America Inc. of Santa Clara, Calif. In some embodiments, thehypervisor may be firmware or hardware or a combination of softwareand/or firmware and/or hardware. The hypervisor provides resources toeach virtual operating system such as a virtual processor, virtualmemory, a virtual network device, and a virtual disk. Each virtualmachine has one or more virtual disks. The hypervisor typically storesthe data of virtual disks in files on the file system of the physicalhost machine, called virtual machine disk files (in VMware lingo) orvirtual hard disk image files (in Microsoft lingo). For example,VMware's ESX Server provides the Virtual Machine File System (VMFS) forthe storage of virtual machine disk files. A virtual machine reads datafrom and writes data to its virtual disk much the e way that a physicalmachine reads data from and writes data to a physical disk. Examples oftechniques for implementing information management in a cloud computingenvironment are described in U.S. Pat. No. 8,285,681. Examples oftechniques for implementing information management in a virtualizedcomputing environment are described in U.S. Pat. No. 8,307,177.

Information management system 100 can also include a variety ofelectronic data storage devices, generally used for mass storage ofdata, including, e.g., primary storage devices 104 and secondary storagedevices 108. Storage devices can generally be of any suitable typeincluding, without limitation, disk drives, storage arrays (e.g.,storage-area network (SAN) and/or network-attached storage (NAS)technology), semiconductor memory (e.g., solid state storage devices),network attached storage (NAS) devices, tape libraries or othermagnetic, non-tape storage devices, optical media storage devices,DNA/RNA-based memory technology, combinations of the same, etc. In someembodiments, storage devices can form part of a distributed file system.In some cases, storage devices are provided in a cloud storageenvironment (e.g., a private cloud or one operated by a third-partyvendor), whether for primary data or secondary copies or both.

Depending on context, the term “information management system” can referto generally all of the illustrated hardware and software components inFIG. 1C, or the term may refer to only a subset of the illustratedcomponents. For instance, in some cases, system 100 generally refers toa combination of specialized components used to protect, move, manage,manipulate, analyze, and/or process data and metadata generated byclient computing devices 102. However, system 100 in some cases does notinclude the underlying components that generate and/or store primarydata 112, such as the client computing devices 102 themselves, and theprimary storage devices 104. Likewise secondary storage devices 108(e.g., a third-party provided cloud storage environment) may not be partof system 100. As an example, “information management system” maysometimes refer to one or more of the following components, which willbe described in further detail below: storage manager, data agent, andmedia agent.

Information management system 100 includes one or more client computingdevices 102 having an operating system and at least one application 110executing thereon; and one or more primary storage devices 104 storingprimary data 112. Client computing device(s) 102 and primary storagedevices 104 may generally be referred to in some cases as primarystorage subsystem 117.

Client Computing Devices, Clients, and Subclients

Typically, a variety of sources in an organization produce data to beprotected and managed. As just one illustrative example, in a corporateenvironment such data sources can be employee workstations and companyservers such as a mail server, a web server, a database server, atransaction server, or the like. In system 100, data generation sourcesinclude one or more client computing devices 102. A computing devicethat has a data agent 142 installed and operating on it is generallyreferred to as a “client computing device” 102, and may include any typeof computing device, without limitation. A client computing device 102may be associated with one or more users and/or user accounts.

A “client” is a logical component of information management system 100,which may represent a logical grouping of one or more agents installedon a client computing device 102. Storage manager 140 recognizes aclient as a component of system 100, and in some embodiments, mayautomatically create a client component the first time a data agent 142is installed on a client computing device 102. Because data generated byexecutable component(s) 110 is tracked by the associated data agent 142so that it may be properly protected in system 100, a client may be saidto generate data and to store the generated data to primary storage,such as primary storage device 104. However, the terms “client” and“client computing device” as used herein do not imply that a clientcomputing device 102 is necessarily configured in the client/serversense relative to another computing device such as a mail server, orthat a client computing device 102 cannot be a server in its own right.As just a few examples, a client computing device 102 can be and/orinclude mail servers, file servers, database servers, and web servers.

Each client computing device 102 may have application(s) 110 executingthereon which generate and manipulate the data that is to be protectedfrom loss and managed in system 100. Applications 110 generallyfacilitate the operations of an organization, and can include, withoutlimitation, mail server applications (e.g., Microsoft Exchange Server),file server applications, mail client applications (e.g., MicrosoftExchange Client), database applications or database management systems(e.g., SQL, Oracle, SAP, Lotus Notes Database), word processingapplications (e.g., Microsoft Word), spreadsheet applications, financialapplications, presentation applications, graphics and/or videoapplications, browser applications, mobile applications, entertainmentapplications, and so on. Each application 110 may be accompanied by anapplication-specific data agent 142. A file system, e.g., MicrosoftWindows Explorer, may be considered an application 110 and may beaccompanied by its own data agent 142. Client computing devices 102 canhave at least one operating system (e.g., Microsoft Windows, Mac OS X,iOS, IBM z/OS, Linux, other Unix-based operating systems, etc.)installed thereon, which may support or host one or more file systemsand other applications 110. In some embodiments, a virtual machine thatexecutes on a host client computing device 102 may be considered anapplication 110 and may be accompanied by a specific data agent 142(e.g., virtual server data agent).

Client computing devices 102 and other components in system 100 can beconnected to one another via one or more electronic communicationpathways 114. For example, a first communication pathway 114 maycommunicatively couple client computing device 102 and secondary storagecomputing device 106; a second communication pathway 114 maycommunicatively couple storage manager 140 and client computing device102; and a third communication pathway 114 may communicatively couplestorage manager 140 and secondary storage computing device 106, etc.(see, e.g., FIG. 1A and FIG. 1C). A communication pathway 114 caninclude one or more networks or other connection types including one ormore of the following, without limitation: the Internet, a wide areanetwork (WAN), a local area network (LAN), a Storage Area Network (SAN),a Fibre Channel (FC) connection, a Small Computer System Interface(SCSI) connection, a virtual private network (VPN), a token ring orTCP/IP based network, an intranet network, a point-to-point link, acellular network, a wireless data transmission system, a two-way cablesystem, an interactive kiosk network, a satellite network, a broadbandnetwork, a baseband network, a neural network, a mesh network, an ad hocnetwork, other appropriate computer or telecommunications networks,combinations of the same or the like. Communication pathways 114 in somecases may also include application programming interfaces (APIs)including, e.g., cloud service provider APIs, virtual machine managementAPIs, and hosted service provider APIs. The underlying infrastructure ofcommunication pathways 114 may be wired and/or wireless, analog and/ordigital, or any combination thereof; and the facilities used may beprivate, public, third-party provided, or any combination thereof,without limitation.

A “subclient” is a logical grouping of all or part of a client's primarydata 112. In general a subclient may be defined according to how thesubclient data is to be protected as a unit in system 100. For example,a subclient may be associated with a certain storage policy. A givenclient may thus comprise several subclients, each subclient associatedwith a different storage policy. For example, some files may form afirst subclient that requires compression and deduplication and isassociated with a first storage policy. Other files of the client mayform a second subclient that requires a different retention schedule aswell as encryption, and may be associated with a different, secondstorage policy. As a result, though the primary data may be generated bythe same application 110, and may belong to one given client, portionsof the data may be assigned to different subclients for distincttreatment by the information management system. More detail onsubclients is given in regard to storage policies below.

Primary Data and Exemplary Primary Storage Devices

Primary data 112 is generally production data or other “live” datagenerated by the operating system and/or applications 110 executing onclient computing device 102. Primary data 112 is generally stored onprimary storage device(s) 104 and is organized via a file systemoperating on the client computing device 102. Thus, client computingdevice(s) 102 and corresponding applications 110 may create, access,modify, write, delete, and otherwise use primary data 112. Primary data112 is generally in the native format of the source application 110.According to certain aspects, primary data 112 is an initial or firststored body of data generated by the source application 110. Primarydata 112 in some cases is created substantially directly from datagenerated by the corresponding source application 110.

Primary storage devices 104 storing primary data 112 may be relativelyfast and/or expensive technology (e.g., a disk drive, a hard-diskstorage array, solid state memory, etc.), typically because they mustsupport high-performance live production environments. Primary data 112may be highly changeable and/or may be intended for relatively shortterm retention (e.g., hours, days, or weeks). According to someembodiments, client computing device 102 can access primary data 112stored in primary storage device 104 by making conventional file systemcalls via the operating system. Primary data 112 may include structureddata (e.g., database files), unstructured data (e.g., documents), and/orsemi-structured data. See, e.g., FIG. 1B.

It can be useful in performing certain tasks to organize primary data112 into units of different granularities. In general, primary data 112can include files, directories, file system volumes, data blocks,extents, or any other hierarchies or organizations of data objects. Asused herein, a “data object” can refer to (i) any file that is currentlyaddressable by a file system or that was previously addressable by thefile system (e.g., an archive file), and (ii) a subset of such a file(e.g., a data block, an extent, etc.).

It can also be useful in performing certain functions of system 100 toaccess and modify metadata within primary data 112. Metadata generallyincludes information about data objects and/or characteristicsassociated with the data objects. For simplicity herein, it is to beunderstood that, unless expressly stated otherwise, any reference toprimary data 112 generally also includes its associated metadata, butreferences to metadata generally do not include the primary data.Metadata can include, without limitation, one or more of the following:the data owner (e.g., the client or user that generates the data), thelast modified time (e.g., the time of the most recent modification ofthe data object), a data object name (e.g., a file name), a data objectsize (e.g., a number of bytes of data), information about the content(e.g., an indication as to the existence of a particular search term),user-supplied tags, to/from information for email (e.g., an emailsender, recipient, etc.), creation date, file type (e.g., format orapplication type), last accessed time, application type (e.g., type ofapplication that generated the data object), location/network (e.g., acurrent, past or future location of the data object and network pathwaysto/from the data object), geographic location (e.g., GPS coordinates),frequency of change (e.g., a period in which the data object ismodified), business unit (e.g., a group or department that generates,manages or is otherwise associated with the data object), aginginformation (e.g., a schedule, such as a time period, in which the dataobject is migrated to secondary or long term storage), boot sectors,partition layouts, file location within a file folder directorystructure, user permissions, owners, groups, access control lists(ACLs), system metadata (e.g., registry information), combinations ofthe same or other similar information related to the data object. Inaddition to metadata generated by or related to file systems andoperating systems, some applications 110 and/or other components ofsystem 100 maintain indices of metadata for data objects, e.g., metadataassociated with individual email messages. The use of metadata toperform classification and other functions is described in greaterdetail below.

Each client computing device 102 is generally associated with and/or incommunication with one or more primary storage devices 104 storingcorresponding primary data 112. A client computing device 102 may beconsidered to be associated with or in communication with a primarystorage device 104 if it is capable of one or more of: routing and/orstoring data (e.g., primary data 112) to the particular primary storagedevice 104, coordinating the routing and/or storing of data to theparticular primary storage device 104, retrieving data from theparticular primary storage device 104, coordinating the retrieval ofdata from the particular primary storage device 104, and modifyingand/or deleting data in the particular primary storage device 104. Aclient computing device 102 may be said to access data stored in anassociated storage device 104.

Primary storage device 104 may be dedicated or shared. In some cases,each primary storage device 104 is dedicated to an associated clientcomputing device 102, e.g., a local disk drive. In other cases, one ormore primary storage devices 104 can be shared by multiple clientcomputing devices 102, e.g., via a local network, in a cloud storageimplementation, etc. As one example, primary storage device 104 can be astorage array shared by a group of client computing devices 102, such asEMC Clariion, EMC Symmetrix, EMC Celerra, Dell EqualLogic, IBM XIV,NetApp FAS, HP EVA, and HP 3PAR.

Information management system 100 may also include hosted services (notshown), which may be hosted in some cases by an entity other than theorganization that employs the other components of system 100. Forinstance, the hosted services may be provided by online serviceproviders. Such service providers can provide social networkingservices, hosted email services, or hosted productivity applications orother hosted applications such as software-as-a-service (SaaS),platform-as-a-service (PaaS), application service providers (ASPs),cloud services, or other mechanisms for delivering functionality via anetwork. As it services users, each hosted service may generateadditional data and metadata, which may be managed by system 100, e.g.,as primary data 112. In some cases, the hosted services may be accessedusing one of the applications 110. As an example, a hosted mail servicemay be accessed via browser running on a client computing device 102.

Secondary Copies and Exemplary Secondary Storage Devices

Primary data 112 stored on primary storage devices 104 may becompromised in some cases, such as when an employee deliberately oraccidentally deletes or overwrites primary data 112. Or primary storagedevices 104 can be damaged, lost, or otherwise corrupted. For recoveryand/or regulatory compliance purposes, it is therefore useful togenerate and maintain copies of primary data 112. Accordingly, system100 includes one or more secondary storage computing devices 106 and oneor more secondary storage devices 108 configured to create and store oneor more secondary copies 116 of primary data 112 including itsassociated metadata. The secondary storage computing devices 106 and thesecondary storage devices 108 may be referred to as secondary storagesubsystem 118.

Creation of secondary copies 116 can help in search and analysis effortsand meet other information management goals as well, such as: restoringdata and/or metadata if an original version is lost (e.g., by deletion,corruption, or disaster); allowing point-in-time recovery; complyingwith regulatory data retention and electronic discovery (e-discovery)requirements; reducing utilized storage capacity in the productionsystem and/or in secondary storage; facilitating organization and searchof data; improving user access to data files across multiple computingdevices and/or hosted services; and implementing data retentionpolicies.

A secondary copy 116 can comprise a separate stored copy of data that isderived from one or more earlier-created stored copies (e.g., derivedfrom primary data 112 or from another secondary copy 116). Secondarycopies 116 can include point-in-time data, and may be intended forrelatively long-term retention, before some or all of the data is movedto other storage or discarded. In some cases, a secondary copy 116 maybe in a different storage device than other previously stored copies;and/or may be remote from other previously stored copies. Secondarycopies 116 can be stored in the same storage device as primary data 112.For example, a disk array capable of performing hardware snapshotsstores primary data 112 and creates and stores hardware snapshots of theprimary data 112 as secondary copies 116. Secondary copies 116 may bestored in relatively slow and/or lower cost storage (e.g., magnetictape). A secondary copy 116 may be stored in a backup or archive format,or in some other format different from the native source applicationformat or other format of primary data 112.

Secondary storage computing devices 106 may index secondary copies 116(e.g., using a media agent 144), so that users can browse and restore ata later time. After creation of a secondary copy 116 representative ofcertain primary data 112, a pointer or other location indicia (e.g., astub) may be placed in primary data 112, or be otherwise associated withprimary data 112, to indicate the current location on secondary storagedevice(s) 108 of a particular secondary copy 116.

Since an instance of a data object or metadata in primary data 112 maychange over time as it is modified by application 110 (or hosted serviceor the operating system), system 100 may create and manage multiplesecondary copies 116 of a particular data object or metadata, each copyrepresenting the state of the data object in primary data 112 at aparticular point in time. Moreover, since an instance of a data objectin primary data 112 may eventually be deleted from primary storagedevice 104 and the file system, system 100 may continue to managepoint-in-time representations of that data object, even though theinstance in primary data 112 no longer exists.

For virtual machines, the operating system and other applications 110 ofclient computing device(s) 102 may execute within or under themanagement of virtualization software (e.g., a VMM), and the primarystorage device(s) 104 may comprise a virtual disk created on a physicalstorage device. System 100 may create secondary copies 116 of the filesor other data objects in a virtual disk file and/or secondary copies 116of the entire virtual disk file itself (e.g., of an entire .vmdk file).

Secondary copies 116 may be distinguished from corresponding primarydata 112. First, secondary copies 116 can be stored in a differentformat (e.g., backup, archive, or other non-native format) than primarydata 112. For this or other reasons, secondary copies 116 may not bedirectly useable by applications 110 or client computing device 102(e.g., via standard system calls or otherwise) without modification,processing, or other intervention by system 100 which may be referred toas “restore” operations. Secondary copies 116 may have been processed bydata agent 142 and/or media agent 144 in the course of being created(e.g., compression, deduplication, encryption, integrity markers,indexing, formatting, etc.), and thus secondary copy 116 may representsource primary data 112 without necessarily being exactly identical tothe source.

Second, secondary copies 116 may be stored on a secondary storage device108 that is inaccessible to application 110 running on client computingdevice 102 and/or hosted service. Some secondary copies 116 may be“offline copies,” in that they are not readily available (e.g., notmounted to tape or disk). Offline copies can include copies of data thatsystem 100 can access without human intervention (e.g., tapes within anautomated tape library, but not yet mounted in a drive), and copies thatthe system 100 can access only with some human intervention (e.g., tapeslocated at an offsite storage site).

Using Intermediate Devices for Creating Secondary Copies—SecondaryStorage Computing Devices

Creating secondary copies can be challenging. For instance, hundreds orthousands of client computing devices 102 may be continually generatinglarge volumes of primary data 112 to be protected. Also, there can besignificant overhead involved in the creation of secondary copies 116.Moreover, secondary storage devices 108 may be special-purposecomponents, and devices that write to, read from, or otherwise interactwith secondary storage devices 108, such as secondary storage computingdevices 106 and corresponding media agents 144, may require specializedprogrammed intelligence and/or hardware capability. Client computingdevices 102 may interact directly with a secondary storage device 108 tocreate secondary copies 116; however, in view of the factors describedabove, this approach can negatively impact the ability of clientcomputing device 102 to serve/service application 110 and produceprimary data 112. Further, any given client computing device 102 may notbe optimized for interaction with certain secondary storage devices 108.

Thus, information management system 100 may include one or more softwareand/or hardware components which generally act as intermediaries betweenclient computing devices 102 (that generate primary data 112) andsecondary storage devices 108 (that store secondary copies 116). Inaddition to off-loading certain responsibilities from client computingdevices 102, these intermediate components can provide other benefits.For instance, as discussed further below with respect to FIG. 1D,distributing some of the work involved in creating secondary copies 116can enhance scalability and improve system performance. For instance,using specialized secondary storage computing devices 106 and mediaagents 144 for interfacing with secondary storage devices 108 and/or forperforming certain data processing operations can greatly improve thespeed with which system 100 performs information management operationsand can also improve the capacity of the system to handle large numbersof such operations, while reducing the computational load on theproduction environment of client computing devices 102. The intermediatecomponents can include one or more secondary storage computing devices106 as shown in FIG. 1A and/or one or more media agents 144. Mediaagents are discussed further below (e.g., with respect to FIGS. 1C 1E).

Secondary storage computing device(s) 106 can comprise any of thecomputing devices described above, without limitation. In some cases,secondary storage computing device(s) 106 also include specializedhardware and/or software componentry for interacting with certainsecondary storage device(s) 108 with which they may be speciallyassociated.

To create a secondary copy 116 involving the copying of data fromprimary storage subsystem 117 to secondary storage subsystem 118, clientcomputing device 102 may communicate the primary data 112 to be copied(or a processed version thereof) to the designated secondary storagecomputing device 106, via a communication pathway 114. Secondary storagecomputing device 106 in turn may perform further processing and mayconvey the data (or a processed version thereof) to secondary storagedevice 108. One or more secondary copies 116 may be created fromexisting secondary copies 116, such as in the case of an auxiliary copyoperation, described further below.

Exemplary Primary Data and an Exemplary Secondary Copy

FIG. 1B is a detailed view showing some specific examples of primarydata stored on primary storage device(s) 104 and secondary copy datastored on secondary storage device(s) 108, with other components of thesystem removed for the purposes of illustration. Stored on the primarystorage device(s) 104 are primary data 112 objects including wordprocessing documents 119A-B, spreadsheets 120, presentation documents122, video files 124, image files 126, email mailboxes 128 (andcorresponding email messages 129A-C), html/xml or other types of markuplanguage files 130, databases 132 and corresponding tables or other datastructures 133A-133C). Some or all primary data 112 objects areassociated with corresponding metadata (e.g., “Meta1-11”), which mayinclude file system metadata and/or application-specific metadata.Stored on the secondary storage device(s) 108 are secondary copy 116data objects 134A-C which may include copies of or may otherwiserepresent corresponding primary data 112.

Secondary copy data objects 134A-C can individually represent more thanone primary data object. For example, secondary copy data object 134Arepresents three separate primary data objects 133C, 122, and 129C(represented as 133C′, 122′, and 129C′, respectively, and accompanied bycorresponding metadata Meta11, Meta3, and Meta8, respectively).Moreover, as indicated by the prime mark (′), secondary storagecomputing devices 106 or other components in secondary storage subsystem118 may process the data received from primary storage subsystem 117 andstore a secondary copy including a transformed and/or supplementedrepresentation of a primary data object and/or metadata that isdifferent from the original format, e.g., in a compressed, encrypted,deduplicated, or other modified format. For instance, secondary storagecomputing devices 106 can generate new metadata or other informationbased on said processing, and store the newly generated informationalong with the secondary copies. Secondary copy data object 1346represents primary data objects 120, 1336, and 119A as 120′, 1336′, and119A′, respectively, accompanied by corresponding metadata Meta2,Meta10, and Meta1, respectively. Also, secondary copy data object 134Crepresents primary data objects 133A, 1196, and 129A as 133A′, 1196′,and 129A′, respectively, accompanied by corresponding metadata Meta9,Meta5, and Meta6, respectively.

Exemplary Information Management System Architecture

Information management system 100 can incorporate a variety of differenthardware and software components, which can in turn be organized withrespect to one another in many different configurations, depending onthe embodiment. There are critical design choices involved in specifyingthe functional responsibilities of the components and the role of eachcomponent in system 100. Such design choices can impact performance aswell as the adaptability of system 100 to data growth and other changingcircumstances.

FIG. 1C shows an information management system 100 designed according tothese considerations and which includes: storage manager 140, one ormore data agents 142 executing on client computing device(s) 102 andconfigured to process primary data 112, and one or more media agents 144executing on the one or more secondary storage computing devices 106 forperforming tasks involving the secondary storage devices 108.

Storage Manager

Storage manager 140 is a centralized storage and/or information managerthat is configured to perform certain control functions and also tostore certain critical information about system 100. As noted, thenumber of components in system 100 and the amount of data undermanagement can be large. Managing the components and data is therefore asignificant task, which can grow unpredictably as the number ofcomponents and data scale to meet the needs of the organization. Forthese and other reasons, according to certain embodiments,responsibility for controlling system 100, or at least a significantportion of that responsibility, is allocated to storage manager 140.Storage manager 140 can be adapted independently according to changingcircumstances, without having to replace or re-design the remainder ofthe system. Moreover, a computing device for hosting and/or operating asstorage manager 140 can be selected to best suit the functions andnetworking needs of storage manager 140. These and other advantages aredescribed in further detail below and with respect to FIG. 1D.

Storage manager 140 may be a software module or other application,which, in some embodiments operates in conjunction with one or moreassociated data structures such as a dedicated database (e.g.,management database 146). In some embodiments, storage manager 140 isitself a computing device that performs the functions described herein.The storage manager generally initiates, performs, coordinates and/orcontrols storage and other information management operations performedby the system 100, e.g., to protect and control primary data 112 andsecondary copies 116. In general, storage manager 100 may be said tomanage information management system 100, which includes managingconstituent components such as data agents and media agents, etc.

As shown by the dashed arrowed lines 114 in FIG. 1C, storage manager 140may communicate with and/or control some or all elements of theinformation management system 100, such as data agents 142 and mediaagents 144. In this manner, storage manager 140 may control theoperation of various hardware and software components in system 100. Incertain embodiments, control information originates from storage manager140 and status as well as index reporting is transmitted to storagemanager 140 by the managed components, whereas payload data and metadataare generally communicated between data agents 142 and media agents 144(or otherwise between client computing device(s) 102 and secondarystorage computing device(s) 106), e.g., at the direction of and underthe management of storage manager 140. Control information can generallyinclude parameters and instructions for carrying out informationmanagement operations, such as, without limitation, instructions toperform a task associated with an operation, timing informationspecifying when to initiate a task, data path information specifyingwhat components to communicate with or access in carrying out anoperation, and the like. In other embodiments, some informationmanagement operations are controlled or initiated by other components ofsystem 100 (e.g., by media agents 144 or data agents 142), instead of orin combination with storage manager 140.

According to certain embodiments, storage manager 140 provides one ormore of the following functions:

communicating with data agents 142 and media agents 144, includingtransmitting instructions, messages, and/or queries, as well asreceiving status reports, index information, messages, and/or queries,and responding to same;

initiating execution of information management operations;

initiating restore and recovery operations;

managing secondary storage devices 108 and inventory/capacity of thesame;

allocating secondary storage devices 108 for secondary copy operations;

reporting, searching, and/or classification of data in system 100;

monitoring completion of and status reporting related to informationmanagement operations and jobs;

tracking movement of data within system 100;

tracking age information relating to secondary copies 116, secondarystorage devices 108, comparing the age information against retentionguidelines, and initiating data pruning when appropriate;

tracking logical associations between components in system 100;

protecting metadata associated with system 100, e.g., in managementdatabase 146;

implementing job management, schedule management, event management,alert management, reporting, job history maintenance, user securitymanagement, disaster recovery management, and/or user interfacing forsystem administrators and/or end users of system 100;

sending, searching, and/or viewing of log files; and

implementing operations management functionality.

Storage manager 140 may maintain an associated database 146 (or “storagemanager database 146” or “management database 146”) ofmanagement-related data and information management policies 148.Database 146 can be stored in computer memory accessible by storagemanager 140. Database 146 may include a management index 150 (or “index150”) or other data structure(s) that may store: logical associationsbetween components of the system; user preferences and/or profiles(e.g., preferences regarding encryption, compression, or deduplicationof primary data or secondary copies; preferences regarding thescheduling, type, or other aspects of secondary copy or otheroperations; mappings of particular information management users or useraccounts to certain computing devices or other components, etc.;management tasks; media containerization; or other useful data. Forexample, storage manager 140 may use index 150 to track logicalassociations between media agents 144 and secondary storage devices 108and/or movement of data from primary storage devices 104 to secondarystorage devices 108. For instance, index 150 may store data associatinga client computing device 102 with a particular media agent 144 and/orsecondary storage device 108, as specified in an information managementpolicy 148.

Administrators and others may configure and initiate certain informationmanagement operations on an individual basis. But while this may beacceptable for some recovery operations or other infrequent tasks, it isoften not workable for implementing on-going organization-wide dataprotection and management. Thus, system 100 may utilize informationmanagement policies 148 for specifying and executing informationmanagement operations on an automated basis. Generally, an informationmanagement policy 148 can include a stored data structure or otherinformation source that specifies parameters (e.g., criteria and rules)associated with storage management or other information managementoperations. Storage manager 140 can process an information managementpolicy 148 and/or index 150 and, based on the results, identify aninformation management operation to perform, identify the appropriatecomponents in system 100 to be involved in the operation (e.g., clientcomputing devices 102 and corresponding data agents 142, secondarystorage computing devices 106 and corresponding media agents 144, etc.),establish connections to those components and/or between thosecomponents, and/or instruct and control those components to carry outthe operation. In this manner, system 100 can translate storedinformation into coordinated activity among the various computingdevices in system 100.

Management database 146 may maintain information management policies 148and associated data, although information management policies 148 can bestored in computer memory at any appropriate location outside managementdatabase 146. For instance, an information management policy 148 such asa storage policy may be stored as metadata in a media agent database 152or in a secondary storage device 108 (e.g., as an archive copy) for usein restore or other information management operations, depending on theembodiment. Information management policies 148 are described furtherbelow. According to certain embodiments, management database 146comprises a relational database (e.g., an SQL database) for trackingmetadata, such as metadata associated with secondary copy operations(e.g., what client computing devices 102 and corresponding subclientdata were protected and where the secondary copies are stored and whichmedia agent 144 performed the secondary storage). This and othermetadata may additionally be stored in other locations, such as atsecondary storage computing device 106 or on the secondary storagedevice 108, allowing data recovery without the use of storage manager140 in some cases. Thus, management database 146 may comprise dataneeded to kick off secondary copy operations (e.g., storage policies),status and reporting information about completed jobs (e.g., status onyesterday's backup jobs), and additional information sufficient toenable restore and disaster recovery operations (e.g., media agentassociations, location indexing, content indexing, etc.)

Storage manager 140 may include a jobs agent 156, a user interface 158,and a management agent 154, all of which may be implemented asinterconnected software modules or application programs. These aredescribed further below.

Jobs agent 156 in some embodiments initiates, controls, and/or monitorsthe status of some or all information management operations previouslyperformed, currently being performed, or scheduled to be performed bysystem 100. A job may be a logical grouping of information managementoperations such as generating backup copies of a primary data 112subclient at a certain time every day. Thus, jobs agent 156 may accessinformation management policies 148 (e.g., in management database 146)to determine when and how to initiate/control jobs in system 100.

Storage Manager User Interfaces

User interface 158 may include information processing and displaysoftware, such as a graphical user interface (GUI), an applicationprogram interface (API), and/or other interactive interface(s) throughwhich users and system processes can retrieve information about thestatus of information management operations or issue instructions tosystem 100 and/or its constituent components. Via user interface 158,users may issue instructions to the components in system 100 regardingperformance of secondary copy and recovery operations. For example, auser may modify a schedule concerning the number of pending secondarycopy operations. As another example, a user may employ the GUI to viewthe status of pending secondary copy jobs or to monitor the status ofcertain components in system 100 (e.g., the amount of capacity left in astorage device). Storage manager 140 may track information that permitsit to select, designate, or otherwise identify content indices,deduplication databases, or similar databases or resources or data setswithin its information management cell (or another cell) to be searchedin response to certain queries. Such queries may be entered by the userby interacting with user interface 158.

Various embodiments of information management system 100 may beconfigured and/or designed to generate user interface data useable forrendering the various interactive user interfaces described. The userinterface data may be used by system 100 and/or by another system,device, and/or software program (for example, a browser program), torender the interactive user interfaces. The interactive user interfacesmay be displayed on, for example, electronic displays (including, forexample, touch-enabled displays), consoles, etc., whetherdirect-connected to storage manager 140 or communicatively coupledremotely, e.g., via an internet connection. The present disclosuredescribes various embodiments of interactive and dynamic userinterfaces, some of which may be generated by user interface agent 158,and which are the result of significant technological development. Theuser interfaces described herein may provide improved human-computerinteractions, allowing for significant cognitive and ergonomicefficiencies and advantages over previous systems, including reducedmental workloads, improved decision-making, and the like. User interface158 may operate in a single integrated view or console (not shown). Theconsole may support a reporting capability for generating a variety ofreports, which may be tailored to a particular aspect of informationmanagement.

User interfaces are not exclusive to storage manager 140 and in someembodiments a user may access information locally from a computingdevice component of system 100. For example, some information pertainingto installed data agents 142 and associated data streams may beavailable from client computing device 102. Likewise, some informationpertaining to media agents 144 and associated data streams may beavailable from secondary storage computing device 106.

Storage Manager Management Agent

Management agent 154 can provide storage manager 140 with the ability tocommunicate with other components within information management system100 and/or with other information management cells via network protocolsand application programming interfaces (APIs) including, e.g., HTTP,HTTPS, FTP, REST, virtualization software APIs, cloud service providerAPIs, and hosted service provider APIs.

Management agent 154 also allows multiple information management cellsto communicate with one another. For example, system 100 in some casesmay be one information management cell in a network of multiple cellsadjacent to one another or otherwise logically related, e.g., in a WANor LAN. With this arrangement, the cells may communicate with oneanother through respective management agents 154. Inter-cellcommunication and hierarchy is described in greater detail in e.g., U.S.Pat. No. 7,343,453.

Information Management Cell

An “information management cell” (or “storage operation cell” or “cell”)may generally include a logical and/or physical grouping of acombination of hardware and software components associated withperforming information management operations on electronic data,typically one storage manager 140 and at least one data agent 142(executing on a client computing device 102) and at least one mediaagent 144 (executing on a secondary storage computing device 106). Forinstance, the components shown in FIG. 1C may together form aninformation management cell. Thus, in some configurations, a system 100may be referred to as an information management cell. A given cell maybe identified by the identity of its storage manager 140, which isgenerally responsible for managing the cell.

Multiple cells may be organized hierarchically, so that cells mayinherit properties from hierarchically superior cells or be controlledby other cells in the hierarchy (automatically or otherwise).Alternatively, in some embodiments, cells may inherit or otherwise beassociated with information management policies, preferences,information management operational parameters, or other properties orcharacteristics according to their relative position in a hierarchy ofcells. Cells may also be organized hierarchically according to function,geography, architectural considerations, or other factors useful ordesirable in performing information management operations. For example,a first cell may represent a geographic segment of an enterprise, suchas a Chicago office, and a second cell may represent a differentgeographic segment, such as a New York City office. Other cells mayrepresent departments within a particular office, e.g., human resources,finance, engineering, etc. Where delineated by function, a first cellmay perform one or more first types of information management operations(e.g., one or more first types of secondary copies at a certainfrequency), and a second cell may perform one or more second types ofinformation management operations (e.g., one or more second types ofsecondary copies at a different frequency and under different retentionrules). In general, the hierarchical information is maintained by one ormore storage managers 140 that manage the respective cells (e.g., incorresponding management database(s) 146).

Data Agents

A variety of different applications 110 can operate on a given clientcomputing device 102, including operating systems, file systems,database applications, e mail applications, and virtual machines, justto name a few. And, as part of the process of creating and restoringsecondary copies 116, the client computing device 102 may be tasked withprocessing and preparing the primary data 112 generated by these variousapplications 110. Moreover, the nature of the processing/preparation candiffer across application types, e.g., due to inherent structural,state, and formatting differences among applications 110 and/or theoperating system of client computing device 102. Each data agent 142 istherefore advantageously configured in some embodiments to assist in theperformance of information management operations based on the type ofdata that is being protected at a client-specific and/orapplication-specific level.

Data agent 142 is a component of information system 100 and is generallydirected by storage manager 140 in creating or restoring secondarycopies 116. Data agent 142 may be a software program (e.g., a set ofexecutable binary files) that executes on the same client computingdevice 102 as the associated application 110 that data agent 142 isconfigured to protect. Data agent 142 is generally responsible formanaging, initiating, or otherwise assisting in the performance ofinformation management operations in reference to its associatedapplication(s) 110 and corresponding primary data 112 which isgenerated/accessed by the particular application(s). For instance, dataagent 142 may take part in copying, archiving, migrating, and/orreplicating of primary data 112 stored in the primary storage device(s)104. Data agent 142 may receive control information from storage manager140, such as commands to transfer copies of data objects and/or metadatato one or more media agents 144. Data agent 142 also may compress,deduplicate, and encrypt primary data 112 before transmitting it tomedia agent 144. Data agent 142 also may receive instructions fromstorage manager 140 to restore (or assist in restoring) a secondary copy116 from secondary storage device 108 to primary storage 104, such thatthe restored data may be accessed by application 110.

Each data agent 142 may be specialized for a particular application 110.For instance, different individual data agents 142 may be designed tohandle Microsoft Exchange data, Lotus Notes data, Microsoft Windows filesystem data, Microsoft Active Directory Objects data, SQL Server data,SharePoint data, Oracle database data, SAP database data, virtualmachines and/or associated data, and other types of data. A file systemdata agent, for example, may handle data files and/or other file systeminformation. If a client computing device 102 has two or more types ofdata 112, a specialized data agent 142 may be used for each data type.For example, to backup, migrate, and/or restore all of the data on aMicrosoft Exchange server, the client computing device 102 may use: aMicrosoft Exchange Mailbox data agent 142 to back up the Exchangemailboxes; a Microsoft Exchange Database data agent 142 to back up theExchange databases; a Microsoft Exchange Public Folder data agent 142 toback up the Exchange Public Folders; and a Microsoft Windows File Systemdata agent 142 to back up the file system of client computing device102. In such embodiments, these specialized data agents 142 may betreated as four separate data agents 142 even though they operate on thesame client computing device 102. Other examples may include archivemanagement data agents such as a migration archiver or a compliancearchiver, Quick Recovery® agents, and continuous data replicationagents. Application-specific data agents 142 can provide improvedperformance as compared to generic agents. For instance, becauseapplication-specific data agents 142 may only handle data for a singlesoftware application, the design of the data agent 142 can bestreamlined. The data agent 142 may therefore execute faster and consumeless persistent storage and/or operating memory than data agentsdesigned to generically accommodate multiple different softwareapplications 110.

Each data agent 142 may be configured to access data and/or metadatastored in the primary storage device(s) 104 associated with data agent142 and its host client computing device 102, and process the dataappropriately. For example, during a secondary copy operation, dataagent 142 may arrange or assemble the data and metadata into one or morefiles having a certain format (e.g., a particular backup or archiveformat) before transferring the file(s) to a media agent 144 or othercomponent. The file(s) may include a list of files or other metadata.

In some embodiments, a data agent 142 may be distributed between clientcomputing device 102 and storage manager 140 (and any other intermediatecomponents) or may be deployed from a remote location or its functionsapproximated by a remote process that performs some or all of thefunctions of data agent 142. In addition, a data agent 142 may performsome functions provided by media agent 144. Other embodiments may employone or more generic data agents 142 that can handle and process datafrom two or more different applications 110, or that can handle andprocess multiple data types, instead of or in addition to usingspecialized data agents 142. For example, one generic data agent 142 maybe used to back up, migrate and restore Microsoft Exchange Mailbox dataand Microsoft Exchange Database data, while another generic data agentmay handle Microsoft Exchange Public Folder data and Microsoft WindowsFile System data.

Media Agents

As noted, off-loading certain responsibilities from client computingdevices 102 to intermediate components such as secondary storagecomputing device(s) 106 and corresponding media agent(s) 144 can providea number of benefits including improved performance of client computingdevice 102, faster information management operations, and enhancedscalability. In one example which will be discussed further below, mediaagent 144 can act as a local cache of recently-copied data and/ormetadata that it stored to secondary storage device(s) 108, thusimproving restore capabilities and performance.

Media agent 144 is a component of information system 100 and isgenerally directed by storage manager 140 in creating or restoringsecondary copies 116. Whereas storage manager 140 generally managesinformation management system 100, media agent 144 provides a portal tosecondary storage devices 108. Media agent 144 may be a software program(e.g., a set of executable binary files) that executes on a secondarystorage computing device 106. Media agent 144 generally manages,coordinates, and facilitates the transmission of data between a clientcomputing device 102 (executing a data agent 142) and secondary storagedevice(s) 108. For instance, other components in the system may interactwith media agent 144 to gain access to data stored on secondary storagedevice(s) 108, (e.g., to browse, read, write, modify, delete, or restoredata). Moreover, media agents 144 can generate and store informationrelating to characteristics of the stored data and/or metadata, or cangenerate and store other types of information that generally providesinsight into the contents of the secondary storage devices 108—generallyreferred to as indexing of the stored secondary copies 116.

Media agents 144 can comprise separate nodes of system 100 (e.g., nodesthat are separate from client computing devices 102, storage manager140, and/or secondary storage devices 108). In general, a node can be alogically and/or physically separate component, and in some cases is acomponent that is individually addressable or otherwise identifiable. Inaddition, each media agent 144 may operate on a dedicated secondarystorage computing device 106, while in other embodiments a plurality ofmedia agents 144 may operate on the same secondary storage computingdevice 106.

A media agent 144 may be associated with a particular secondary storagedevice 108 if that media agent 144 is capable of one or more of: routingand/or storing data to the particular secondary storage device 108;coordinating the routing and/or storing of data to the particularsecondary storage device 108; retrieving data from the particularsecondary storage device 108; coordinating the retrieval of data fromthe particular secondary storage device 108; and modifying and/ordeleting data retrieved from the particular secondary storage device108. Media agent 144 in certain embodiments is physically separate fromthe associated secondary storage device 108. For instance, a media agent144 may operate on a secondary storage computing device 106 in adistinct housing, package, and/or location from the associated secondarystorage device 108. In one example, a media agent 144 operates on afirst server computer and is in communication with a secondary storagedevice(s) 108 operating in a separate rack-mounted RAID-based system.

A media agent 144 associated with a particular secondary storage device108 may instruct secondary storage device 108 to perform an informationmanagement task. For instance, a media agent 144 may instruct a tapelibrary to use a robotic arm or other retrieval means to load or eject acertain storage media, and to subsequently archive, migrate, or retrievedata to or from that media, e.g., for the purpose of restoring data to aclient computing device 102. As another example, a secondary storagedevice 108 may include an array of hard disk drives or solid statedrives organized in a RAID configuration, and media agent 144 mayforward a logical unit number (LUN) and other appropriate information tothe array, which uses the received information to execute the desiredsecondary copy operation. Media agent 144 may communicate with asecondary storage device 108 via a suitable communications link, such asa SCSI or Fiber Channel link.

Each media agent 144 may maintain an associated media agent database152. Media agent database 152 may be stored to a disk or other storagedevice (not shown) that is local to the secondary storage computingdevice 106 on which media agent 144 operates. In other cases, mediaagent database 152 is stored separately from the host secondary storagecomputing device 106. Media agent database 152 can include, among otherthings, a media agent index 153 (see, e.g., FIG. 1C). In some cases,media agent index 153 does not form a part of and is instead separatefrom media agent database 152.

Media agent index 153 (or “index 153”) may be a data structureassociated with the particular media agent 144 that includes informationabout the stored data associated with the particular media agent andwhich may be generated in the course of performing a secondary copyoperation or a restore. Index 153 provides a fast and efficientmechanism for locating/browsing secondary copies 116 or other datastored in secondary storage devices 108 without having to accesssecondary storage device 108 to retrieve the information from there. Forinstance, for each secondary copy 116, index 153 may include metadatasuch as a list of the data objects (e.g., files/subdirectories, databaseobjects, mailbox objects, etc.), a logical path to the secondary copy116 on the corresponding secondary storage device 108, locationinformation (e.g., offsets) indicating where the data objects are storedin the secondary storage device 108, when the data objects were createdor modified, etc. Thus, index 153 includes metadata associated with thesecondary copies 116 that is readily available for use from media agent144. In some embodiments, some or all of the information in index 153may instead or additionally be stored along with secondary copies 116 insecondary storage device 108. In some embodiments, a secondary storagedevice 108 can include sufficient information to enable a “bare metalrestore,” where the operating system and/or software applications of afailed client computing device 102 or another target may beautomatically restored without manually reinstalling individual softwarepackages (including operating systems).

Because index 153 may operate as a cache, it can also be referred to asan “index cache.” In such cases, information stored in index cache 153typically comprises data that reflects certain particulars aboutrelatively recent secondary copy operations. After some triggeringevent, such as after some time elapses or index cache 153 reaches aparticular size, certain portions of index cache 153 may be copied ormigrated to secondary storage device 108, e.g., on a least-recently-usedbasis. This information may be retrieved and uploaded back into indexcache 153 or otherwise restored to media agent 144 to facilitateretrieval of data from the secondary storage device(s) 108. In someembodiments, the cached information may include format orcontainerization information related to archives or other files storedon storage device(s) 108.

In some alternative embodiments media agent 144 generally acts as acoordinator or facilitator of secondary copy operations between clientcomputing devices 102 and secondary storage devices 108, but does notactually write the data to secondary storage device 108. For instance,storage manager 140 (or media agent 144) may instruct a client computingdevice 102 and secondary storage device 108 to communicate with oneanother directly. In such a case, client computing device 102 transmitsdata directly or via one or more intermediary components to secondarystorage device 108 according to the received instructions, and viceversa. Media agent 144 may still receive, process, and/or maintainmetadata related to the secondary copy operations, i.e., may continue tobuild and maintain index 153. In these embodiments, payload data canflow through media agent 144 for the purposes of populating index 153,but not for writing to secondary storage device 108.

Media agent 144 and/or other components such as storage manager 140 mayin some cases incorporate additional functionality, such as dataclassification, content indexing, deduplication, encryption,compression, and the like. Further details regarding these and otherfunctions are described below.

Distributed, Scalable Architecture

As described, certain functions of system 100 can be distributed amongstvarious physical and/or logical components. For instance, one or more ofstorage manager 140, data agents 142, and media agents 144 may operateon computing devices that are physically separate from one another. Thisarchitecture can provide a number of benefits. For instance, hardwareand software design choices for each distributed component can betargeted to suit its particular function. The secondary computingdevices 106 on which media agents 144 operate can be tailored forinteraction with associated secondary storage devices 108 and providefast index cache operation, among other specific tasks. Similarly,client computing device(s) 102 can be selected to effectively serviceapplications 110 in order to efficiently produce and store primary data112.

Moreover, in some cases, one or more of the individual components ofinformation management system 100 can be distributed to multipleseparate computing devices. As one example, for large file systems wherethe amount of data stored in management database 146 is relativelylarge, database 146 may be migrated to or may otherwise reside on aspecialized database server (e.g., an SQL server) separate from a serverthat implements the other functions of storage manager 140. Thisdistributed configuration can provide added protection because database146 can be protected with standard database utilities (e.g., SQL logshipping or database replication) independent from other functions ofstorage manager 140. Database 146 can be efficiently replicated to aremote site for use in the event of a disaster or other data loss at theprimary site. Or database 146 can be replicated to another computingdevice within the same site, such as to a higher performance machine inthe event that a storage manager host computing device can no longerservice the needs of a growing system 100.

The distributed architecture also provides scalability and efficientcomponent utilization. FIG. 1D shows an embodiment of informationmanagement system 100 including a plurality of client computing devices102 and associated data agents 142 as well as a plurality of secondarystorage computing devices 106 and associated media agents 144.Additional components can be added or subtracted based on the evolvingneeds of system 100. For instance, depending on where bottlenecks areidentified, administrators can add additional client computing devices102, secondary storage computing devices 106, and/or secondary storagedevices 108. Moreover, where multiple fungible components are available,load balancing can be implemented to dynamically address identifiedbottlenecks. As an example, storage manager 140 may dynamically selectwhich media agents 144 and/or secondary storage devices 108 to use forstorage operations based on a processing load analysis of media agents144 and/or secondary storage devices 108, respectively.

Where system 100 includes multiple media agents 144 (see, e.g., FIG.1D), a first media agent 144 may provide failover functionality for asecond failed media agent 144. In addition, media agents 144 can bedynamically selected to provide load balancing. Each client computingdevice 102 can communicate with, among other components, any of themedia agents 144, e.g., as directed by storage manager 140. And eachmedia agent 144 may communicate with, among other components, any ofsecondary storage devices 108, e.g., as directed by storage manager 140.Thus, operations can be routed to secondary storage devices 108 in adynamic and highly flexible manner, to provide load balancing, failover,etc. Further examples of scalable systems capable of dynamic storageoperations, load balancing, and failover are provided in U.S. Pat. No.7,246,207.

While distributing functionality amongst multiple computing devices canhave certain advantages, in other contexts it can be beneficial toconsolidate functionality on the same computing device. In alternativeconfigurations, certain components may reside and execute on the samecomputing device. As such, in other embodiments, one or more of thecomponents shown in FIG. 1C may be implemented on the same computingdevice. In one configuration, a storage manager 140, one or more dataagents 142, and/or one or more media agents 144 are all implemented onthe same computing device. In other embodiments, one or more data agents142 and one or more media agents 144 are implemented on the samecomputing device, while storage manager 140 is implemented on a separatecomputing device, etc. without limitation.

Exemplary Types of Information Management Operations

In order to protect and leverage stored data, system 100 can beconfigured to perform a variety of information management operations,which may also be referred to in some cases as storage managementoperations or storage operations. These operations can generally include(i) data movement operations, (ii) processing and data manipulationoperations, and (iii) analysis, reporting, and management operations.

Data Movement Operations, Including Secondary Copy Operations

Data movement operations are generally operations that involve thecopying or migration of data between different locations in system 100.For example, data movement operations can include operations in whichstored data is copied, migrated, or otherwise transferred from one ormore first storage devices to one or more second storage devices, suchas from primary storage device(s) 104 to secondary storage device(s)108, from secondary storage device(s) 108 to different secondary storagedevice(s) 108, from secondary storage devices 108 to primary storagedevices 104, or from primary storage device(s) 104 to different primarystorage device(s) 104, or in some cases within the same primary storagedevice 104 such as within a storage array.

Data movement operations can include by way of example, backupoperations, archive operations, information lifecycle managementoperations such as hierarchical storage management operations,replication operations (e.g., continuous data replication), snapshotoperations, deduplication or single instancing operations, auxiliarycopy operations, disaster-recovery copy operations, and the like. Aswill be discussed, some of these operations do not necessarily createdistinct copies. Nonetheless, some or all of these operations aregenerally referred to as “secondary copy operations” for simplicity.Data movement also comprises restoring secondary copies.

Backup Operations

A backup operation creates a copy of a version of primary data 112 at aparticular point in time (e.g., one or more files or other data units).Each subsequent backup copy 116 (which is a form of secondary copy 116)may be maintained independently of the first. A backup generallyinvolves maintaining a version of the copied primary data 112 as well asbackup copies 116. Further, a backup copy in some embodiments isgenerally stored in a form that is different from the native format,e.g., a backup format. This contrasts to the version in primary data 112which may instead be stored in a native format of the sourceapplication(s) 110. In various cases, backup copies can be stored in aformat in which the data is compressed, encrypted, deduplicated, and/orotherwise modified from the original native application format. Forexample, a backup copy may be stored in a compressed backup format thatfacilitates efficient long-term storage.

Backup copies 116 can have relatively long retention periods as comparedto primary data 112, which is generally highly changeable. Backup copies116 may be stored on media with slower retrieval times than primarystorage device 104. Some backup copies may have shorter retentionperiods than some other types of secondary copies 116, such as archivecopies (described below). Backups may be stored at an offsite location.

Backup operations can include full backups, differential backups,incremental backups, “synthetic full” backups, and/or creating a“reference copy.” A full backup (or “standard full backup”) in someembodiments is generally a complete image of the data to be protected.However, because full backup copies can consume a relatively largeamount of storage, it can be useful to use a full backup copy as abaseline and only store changes relative to the full backup copy forsubsequent backup copies.

A differential backup operation (or cumulative incremental backupoperation) tracks and stores changes that occurred since the last fullbackup. Differential backups can grow quickly in size, but can restorerelatively efficiently because a restore can be completed in some casesusing only the full backup copy and the latest differential copy.

An incremental backup operation generally tracks and stores changessince the most recent backup copy of any type, which can greatly reducestorage utilization. In some cases, however, restoring can be lengthycompared to full or differential backups because completing a restoreoperation may involve accessing a full backup in addition to multipleincremental backups.

Synthetic full backups generally consolidate data without directlybacking up data from the client computing device. A synthetic fullbackup is created from the most recent full backup (i.e., standard orsynthetic) and subsequent incremental and/or differential backups. Theresulting synthetic full backup is identical to what would have beencreated had the last backup for the subclient been a standard fullbackup. Unlike standard full, incremental, and differential backups,however, a synthetic full backup does not actually transfer data fromprimary storage to the backup media, because it operates as a backupconsolidator. A synthetic full backup extracts the index data of eachparticipating subclient. Using this index data and the previously backedup user data images, it builds new full backup images (e.g., bitmaps),one for each subclient. The new backup images consolidate the index anduser data stored in the related incremental, differential, and previousfull backups into a synthetic backup file that fully represents thesubclient (e.g., via pointers) but does not comprise all its constituentdata.

Any of the above types of backup operations can be at the volume level,file level, or block level. Volume level backup operations generallyinvolve copying of a data volume (e.g., a logical disk or partition) asa whole. In a file-level backup, information management system 100generally tracks changes to individual files and includes copies offiles in the backup copy. For block-level backups, files are broken intoconstituent blocks, and changes are tracked at the block level. Uponrestore, system 100 reassembles the blocks into files in a transparentfashion. Far less data may actually be transferred and copied tosecondary storage devices 108 during a file-level copy than avolume-level copy. Likewise, a block-level copy may transfer less datathan a file-level copy, resulting in faster execution. However,restoring a relatively higher-granularity copy can result in longerrestore times. For instance, when restoring a block-level copy, theprocess of locating constituent blocks can sometimes take longer thanrestoring file-level backups.

A reference copy may comprise copy(ies) of selected objects from backedup data, typically to help organize data by keeping contextualinformation from multiple sources together, and/or help retain specificdata for a longer period of time, such as for legal hold needs. Areference copy generally maintains data integrity, and when the data isrestored, it may be viewed in the same format as the source data. Insome embodiments, a reference copy is based on a specialized client,individual subclient and associated information management policies(e.g., storage policy, retention policy, etc.) that are administeredwithin system 100.

Archive Operations

Because backup operations generally involve maintaining a version of thecopied primary data 112 and also maintaining backup copies in secondarystorage device(s) 108, they can consume significant storage capacity. Toreduce storage consumption, an archive operation according to certainembodiments creates an archive copy 116 by both copying and removingsource data. Or, seen another way, archive operations can involve movingsome or all of the source data to the archive destination. Thus, datasatisfying criteria for removal (e.g., data of a threshold age or size)may be removed from source storage. The source data may be primary data112 or a secondary copy 116, depending on the situation. As with backupcopies, archive copies can be stored in a format in which the data iscompressed, encrypted, deduplicated, and/or otherwise modified from theformat of the original application or source copy. In addition, archivecopies may be retained for relatively long periods of time (e.g., years)and, in some cases are never deleted. Archive copies are generallyretained for longer periods of time than backup copies. In certainembodiments, archive copies may be made and kept for extended periods inorder to meet compliance regulations.

Archiving can also serve the purpose of freeing up space in primarystorage device(s) 104 and easing the demand on computational resourceson client computing device 102. Similarly, when a secondary copy 116 isarchived, the archive copy can therefore serve the purpose of freeing upspace in the source secondary storage device(s) 108. Examples of dataarchiving operations are provided in U.S. Pat. No. 7,107,298.

Snapshot Operations

Snapshot operations can provide a relatively lightweight, efficientmechanism for protecting data. From an end user viewpoint, a snapshotmay be thought of as an “instant” image of primary data 112 at a givenpoint in time, and may include state and/or status information relativeto an application 110 that creates/manages primary data 112. In oneembodiment, a snapshot may generally capture the directory structure ofan object in primary data 112 such as a file or volume or other data setat a particular moment in time and may also preserve file attributes andcontents. A snapshot in some cases is created relatively quickly, e.g.,substantially instantly, using a minimum amount of file space, but maystill function as a conventional file system backup.

A “hardware snapshot” (or “hardware-based snapshot”) operation can be asnapshot operation where a target storage device (e.g., a primarystorage device 104 or a secondary storage device 108) performs thesnapshot operation in a self-contained fashion, substantiallyindependently, using hardware, firmware and/or software operating on thestorage device itself. For instance, the storage device may performsnapshot operations generally without intervention or oversight from anyof the other components of the system 100, e.g., a storage array maygenerate an “array-created” hardware snapshot and may also manage itsstorage, integrity, versioning, etc. In this manner, hardware snapshotscan off-load other components of system 100 from processing involved increating and managing snapshots.

A “software snapshot” (or “software-based snapshot”) operation, on theother hand, can be a snapshot operation in which one or more othercomponents in information management system 100 (e.g., client computingdevices 102, data agents 142, etc.) implement a software layer thatmanages the snapshot operation via interaction with the target storagedevice. For instance, the component executing the snapshot managementsoftware layer may derive a set of pointers and/or data that representsthe snapshot. The snapshot management software layer may then transmitthe same to the target storage device, along with appropriateinstructions for writing the snapshot. One example of a softwaresnapshot product may be Microsoft Volume Snapshot Service (VSS), whichis part of the Microsoft Windows operating system.

Some types of snapshots do not actually create another physical copy ofall the data as it existed at the particular point in time, but maysimply create pointers that are able to map files and directories tospecific memory locations (e.g., to specific disk blocks) where the dataresides, as it existed at the particular point in time. For example, asnapshot copy may include a set of pointers derived from the file systemor from an application. In some other cases, the snapshot may be createdat the block level, such that creation of the snapshot occurs withoutawareness of the file system. Each pointer points to a respective storeddata block, so that collectively, the set of pointers reflect thestorage location and state of the data object (e.g., file(s) orvolume(s) or data set(s)) at the particular point in time when thesnapshot copy was created.

An initial snapshot may use only a small amount of disk space needed torecord a mapping or other data structure representing or otherwisetracking the blocks that correspond to the current state of the filesystem. Additional disk space is usually required only when files anddirectories change later on. Furthermore, when files change, typicallyonly the pointers which map to blocks are copied, not the blocksthemselves. For example for “copy-on-write” snapshots, when a blockchanges in primary storage, the block is copied to secondary storage orcached in primary storage before the block is overwritten in primarystorage, and the pointer to that block is changed to reflect the newlocation of that block. The snapshot mapping of file system data mayalso be updated to reflect the changed block(s) at that particular pointin time. In some other cases, a snapshot includes a full physical copyof all or substantially all of the data represented by the snapshot.Further examples of snapshot operations are provided in U.S. Pat. No.7,529,782.

A snapshot copy in many cases can be made quickly and withoutsignificantly impacting primary computing resources because largeamounts of data need not be copied or moved. In some embodiments, asnapshot may exist as a virtual file system, parallel to the actual filesystem. Users in some cases gain read-only access to the record of filesand directories of the snapshot. By electing to restore primary data 112from a snapshot taken at a given point in time, users may also returnthe current file system to the state of the file system that existedwhen the snapshot was taken.

Replication Operations

Another type of secondary copy operation is a replication operation.Some types of secondary copies 116 are used to periodically captureimages of primary data 112 at particular points in time (e.g., backups,archives, and snapshots). However, it can also be useful for recoverypurposes to protect primary data 112 in a more continuous fashion, byreplicating primary data 112 substantially as changes occur. In somecases a replication copy can be a mirror copy, for instance, wherechanges made to primary data 112 are mirrored or substantiallyimmediately copied to another location (e.g., to secondary storagedevice(s) 108). By copying each write operation to the replication copy,two storage systems are kept synchronized or substantially synchronizedso that they are virtually identical at approximately the same time.Where entire disk volumes are mirrored, however, mirroring can requiresignificant amount of storage space and utilizes a large amount ofprocessing resources.

According to some embodiments secondary copy operations are performed onreplicated data that represents a recoverable state, or “known goodstate” of a particular application running on the source system. Forinstance, in certain embodiments, known good replication copies may beviewed as copies of primary data 112. This feature allows the system todirectly access, copy, restore, backup or otherwise manipulate thereplication copies as if the data were the “live” primary data 112. Thiscan reduce access time, storage utilization, and impact on sourceapplications 110, among other benefits. Based on known good stateinformation, system 100 can replicate sections of application data thatrepresent a recoverable state rather than rote copying of blocks ofdata. Examples of replication operations (e.g., continuous datareplication) are provided in U.S. Pat. No. 7,617,262.

Deduplication/Single-Instancing Operations

Deduplication or single-instance storage is useful to reduce the amountof non-primary data. For instance, some or all of the above-describedsecondary copy operations can involve deduplication in some fashion. Newdata is read, broken down into data portions of a selected granularity(e.g., sub-file level blocks, files, etc.), compared with correspondingportions that are already in secondary storage, and only new portionsare stored. Portions that already exist are represented as pointers tothe already-stored data. Thus, a deduplicated secondary copy 116 maycomprise actual data portions copied from primary data 112 and mayfurther comprise pointers to already-stored data, which is generallymore storage-efficient than a full copy.

In order to streamline the comparison process, information managementsystem 100 may calculate and/or store signatures (e.g., hashes orcryptographically unique IDs) corresponding to the individual dataportions in the source data and compare the signatures instead ofcomparing entire data portions. In some cases, only a single instance ofeach data portion is stored, and deduplication operations may thereforebe referred to interchangeably as “single-instancing” operations.Depending on the implementation, however, deduplication operations canstore more than one instance of certain data portions, but nonethelesssignificantly reduce stored-data redundancy. Depending on theembodiment, deduplication portions such as data blocks can be of fixedor variable length. Using variable length blocks can enhancededuplication by responding to changes in the data stream, but caninvolve complex processing. In some cases, system 100 utilizes atechnique for dynamically aligning deduplication blocks based onchanging content in the data stream, as described in U.S. Pat. No.8,364,652.

Information management system 100 can perform deduplication in a varietyof manners at a variety of locations. For instance, in some embodiments,system 100 implements “target-side” deduplication by deduplicating dataat the media agent 144 after being received from data agent 142. In somesuch cases, the media agents 144 are generally configured to manage thededuplication process. For instance, one or more of the media agents 144maintain a corresponding deduplication database that storesdeduplication information (e.g., datablock signatures). Examples of sucha configuration are provided in U.S. Pat. Pub. No. 2012/0150826. Insteadof or in combination with “target-side” deduplication, deduplication canalso be performed on the “source-side” (or “client-side”), e.g., toreduce the amount of data to be transmitted by data agent 142 to mediaagent 144. Storage manager 140 may communicate with other componentswithin system 100 via network protocols and cloud service provider APIsto facilitate cloud-based deduplication/single instancing, asexemplified in U.S. Pat. Pub. No. 2012/0150818. Some otherdeduplication/single instancing techniques are described in U.S. Pat.Pub. Nos. 2006/0224846 and 2009/0319534.

Information Lifecycle Management and Hierarchical Storage Management

In some embodiments, files and other data over their lifetime move frommore expensive quick-access storage to less expensive slower-accessstorage. Operations associated with moving data through various tiers ofstorage are sometimes referred to as information lifecycle management(ILM) operations.

One type of ILM operation is a hierarchical storage management (HSM)operation, which generally automatically moves data between classes ofstorage devices, such as from high-cost to low-cost storage devices. Forinstance, an HSM operation may involve movement of data from primarystorage devices 104 to secondary storage devices 108, or between tiersof secondary storage devices 108. With each tier, the storage devicesmay be progressively cheaper, have relatively slower access/restoretimes, etc. For example, movement of data between tiers may occur asdata becomes less important over time. In some embodiments, an HSMoperation is similar to archiving in that creating an HSM copy may(though not always) involve deleting some of the source data, e.g.,according to one or more criteria related to the source data. Forexample, an HSM copy may include primary data 112 or a secondary copy116 that is larger than a given size threshold or older than a given agethreshold. Often, and unlike some types of archive copies, HSM data thatis removed or aged from the source is replaced by a logical referencepointer or stub. The reference pointer or stub can be stored in theprimary storage device 104 or other source storage device, such as asecondary storage device 108 to replace the deleted source data and topoint to or otherwise indicate the new location in (another) secondarystorage device 108.

According to one example, files are generally moved between higher andlower cost storage depending on how often the files are accessed. When auser requests access to HSM data that has been removed or migrated,system 100 uses the stub to locate the data and may make recovery of thedata appear transparent, even though the HSM data may be stored at alocation different from other source data. In this manner, the dataappears to the user (e.g., in file system browsing windows and the like)as if it still resides in the source location (e.g., in a primarystorage device 104). The stub may also include some metadata associatedwith the corresponding data, so that a file system and/or applicationcan provide some information about the data object and/or alimited-functionality version (e.g., a preview) of the data object.

An HSM copy may be stored in a format other than the native applicationformat (e.g., compressed, encrypted, deduplicated, and/or otherwisemodified). In some cases, copies which involve the removal of data fromsource storage and the maintenance of stub or other logical referenceinformation on source storage may be referred to generally as “on-linearchive copies”. On the other hand, copies which involve the removal ofdata from source storage without the maintenance of stub or otherlogical reference information on source storage may be referred to as“off-line archive copies”. Examples of HSM and ILM techniques areprovided in U.S. Pat. No. 7,343,453.

Auxiliary Copy Operations

An auxiliary copy is generally a copy of an existing secondary copy 116.For instance, an initial secondary copy 116 may be derived from primarydata 112 or from data residing in secondary storage subsystem 118,whereas an auxiliary copy is generated from the initial secondary copy116. Auxiliary copies provide additional standby copies of data and mayreside on different secondary storage devices 108 than the initialsecondary copies 116. Thus, auxiliary copies can be used for recoverypurposes if initial secondary copies 116 become unavailable. Exemplaryauxiliary copy techniques are described in further detail in U.S. Pat.No. 8,230,195.

Disaster-Recovery Copy Operations

Information management system 100 may also make and retain disasterrecovery copies, often as secondary, high availability disk copies.System 100 may create secondary disk copies and store the copies atdisaster recovery locations using auxiliary copy or replicationoperations, such as continuous data replication technologies. Dependingon the particular data protection goals, disaster recovery locations canbe remote from the client computing devices 102 and primary storagedevices 104, remote from some or all of the secondary storage devices108, or both.

Data Manipulation, Including Encryption and Compression

Data manipulation and processing may include encryption and compressionas well as integrity marking and checking, formatting for transmission,formatting for storage, etc. Data may be manipulated “client-side” bydata agent 142 as well as “target-side” by media agent 144 in the courseof creating secondary copy 116.

Encryption Operations

Information management system 100 in some cases is configured to processdata (e.g., files or other data objects, primary data 112, secondarycopies 116, etc.), according to an appropriate encryption algorithm(e.g., Blowfish, Advanced Encryption Standard (AES), Triple DataEncryption Standard (3-DES), etc.) to limit access and provide datasecurity. System 100 in some cases encrypts the data at the clientlevel, such that client computing devices 102 (e.g., data agents 142)encrypt the data prior to transferring it to other components, e.g.,before sending the data to media agents 144 during a secondary copyoperation. In such cases, client computing device 102 may maintain orhave access to an encryption key or passphrase for decrypting the dataupon restore. Encryption can also occur when media agent 144 createsauxiliary copies or archive copies. Encryption may be applied increating a secondary copy 116 of a previously unencrypted secondary copy116, without limitation. In further embodiments, secondary storagedevices 108 can implement built-in, high performance hardware-basedencryption.

Compression Operations

Similar to encryption, system 100 may also or alternatively compressdata in the course of generating a secondary copy 116. Compressionencodes information such that fewer bits are needed to represent theinformation as compared to the original representation. Compressiontechniques are well known in the art. Compression operations may applyone or more data compression algorithms. Compression may be applied increating a secondary copy 116 of a previously uncompressed secondarycopy, e.g., when making archive copies or disaster recovery copies. Theuse of compression may result in metadata that specifies the nature ofthe compression, so that data may be uncompressed on restore ifappropriate.

Data Analysis, Reporting, and Management Operations

Data analysis, reporting, and management operations can differ from datamovement operations in that they do not necessarily involve copying,migration or other transfer of data between different locations in thesystem. For instance, data analysis operations may involve processing(e.g., offline processing) or modification of already stored primarydata 112 and/or secondary copies 116. However, in some embodiments dataanalysis operations are performed in conjunction with data movementoperations. Some data analysis operations include content indexingoperations and classification operations which can be useful inleveraging the data under management to provide enhanced search andother features. Other data analysis operations such as compression andencryption can provide data reduction and security benefits,respectively.

Classification Operations/Content Indexing

In some embodiments, information management system 100 analyzes andindexes characteristics, content, and metadata associated with primarydata 112 (“online content indexing”) and/or secondary copies 116(“off-line content indexing”). Content indexing can identify files orother data objects based on content (e.g., user-defined keywords orphrases, other keywords/phrases that are not defined by a user, etc.),and/or metadata (e.g., email metadata such as “to”, “from,” “cc,” “bcc,”attachment name, received time, etc.). Content indexes may be searchedand search results may be restored.

Information management system 100 generally organizes and catalogues theresults into a content index, which may be stored within media agentdatabase 152, for example. The content index can also include thestorage locations of or pointer references to indexed data in primarydata 112 or secondary copies 116, as appropriate. The results may alsobe stored elsewhere in system 100 (e.g., in primary storage device 104or in secondary storage device 108). Such content index data providesstorage manager 140 or other components with an efficient mechanism forlocating primary data 112 and/or secondary copies 116 of data objectsthat match particular criteria, thus greatly increasing the search speedcapability of system 100. For instance, search criteria can be specifiedby a user through user interface 158 of storage manager 140. Moreover,when system 100 analyzes data and/or metadata in secondary copies 116 tocreate an “off-line content index,” this operation has no significantimpact on the performance of client computing devices 102 and thus doesnot take a toll on the production environment. Examples of contentindexing techniques are provided in U.S. Pat. No. 8,170,995.

One or more components, such as a content index engine, can beconfigured to scan data and/or associated metadata for classificationpurposes to populate a database (or other data structure) ofinformation, which can be referred to as a “data classificationdatabase” or a “metabase.” Depending on the embodiment, the dataclassification database(s) can be organized in a variety of differentways, including centralization, logical sub-divisions, and/or physicalsub-divisions. For instance, one or more data classification databasesmay be associated with different subsystems or tiers within system 100.As an example, there may be a first metabase associated with primarystorage subsystem 117 and a second metabase associated with secondarystorage subsystem 118. In other cases, there may be one or moremetabases associated with individual components, e.g., client computingdevices 102 and/or media agents 144. In some embodiments, a dataclassification database may reside as one or more data structures withinmanagement database 146, or may be otherwise associated with storagemanager 140 or may reside as a separate component.

In some cases, metabase(s) may be included in separate database(s)and/or on separate storage device(s) from primary data 112 and/orsecondary copies 116, such that operations related to the metabase(s) donot significantly impact performance on other components of informationmanagement system 100. In other cases, metabase(s) may be stored alongwith primary data 112 and/or secondary copies 116. Files or other dataobjects can be associated with identifiers (e.g., tag entries, etc.) tofacilitate searches of stored data objects. Among a number of otherbenefits, the metabase can also allow efficient, automaticidentification of files or other data objects to associate withsecondary copy or other information management operations. For instance,a metabase can dramatically improve the speed with which the informationmanagement system can search through and identify data as compared toother approaches which can involve scanning an entire file system.Examples of metabases and data classification operations are provided inU.S. Pat. Nos. 7,734,669 and 7,747,579.

Management and Reporting Operations

Certain embodiments leverage the integrated ubiquitous nature ofinformation management system 100 to provide useful system-widemanagement and reporting functions. Operations management can generallyinclude monitoring and managing the health and performance of system 100by, without limitation, performing error tracking, generating granularstorage/performance metrics (e.g., job success/failure information,deduplication efficiency, etc.), generating storage modeling and costinginformation, and the like. As an example, storage manager 140 or othercomponent in system 100 may analyze traffic patterns and suggest and/orautomatically route data to minimize congestion. In some embodiments,the system can generate predictions relating to storage operations orstorage operation information. Such predictions, which may be based on atrending analysis, may predict various network operations or resourceusage, such as network traffic levels, storage media use, use ofbandwidth of communication links, use of media agent components, etc.Further examples of traffic analysis, trend analysis, predictiongeneration, and the like are described in U.S. Pat. No. 7,343,453.

In some configurations having a hierarchy of storage operation cells, amaster storage manager 140 may track the status of subordinate cells,such as the status of jobs, system components, system resources, andother items, by communicating with storage managers 140 (or othercomponents) in the respective storage operation cells. Moreover, themaster storage manager 140 may also track status by receiving periodicstatus updates from the storage managers 140 (or other components) inthe respective cells regarding jobs, system components, systemresources, and other items. In some embodiments, a master storagemanager 140 may store status information and other information regardingits associated storage operation cells and other system information inits management database 146 and/or index 150 (or in another location).The master storage manager 140 or other component may also determinewhether certain storage-related or other criteria are satisfied, and mayperform an action or trigger event (e.g., data migration) in response tothe criteria being satisfied, such as where a storage threshold is metfor a particular volume, or where inadequate protection exists forcertain data. For instance, data from one or more storage operationcells is used to dynamically and automatically mitigate recognizedrisks, and/or to advise users of risks or suggest actions to mitigatethese risks. For example, an information management policy may specifycertain requirements (e.g., that a storage device should maintain acertain amount of free space, that secondary copies should occur at aparticular interval, that data should be aged and migrated to otherstorage after a particular period, that data on a secondary volumeshould always have a certain level of availability and be restorablewithin a given time period, that data on a secondary volume may bemirrored or otherwise migrated to a specified number of other volumes,etc.). If a risk condition or other criterion is triggered, the systemmay notify the user of these conditions and may suggest (orautomatically implement) a mitigation action to address the risk. Forexample, the system may indicate that data from a primary copy 112should be migrated to a secondary storage device 108 to free space onprimary storage device 104. Examples of the use of risk factors andother triggering criteria are described in U.S. Pat. No. 7,343,453.

In some embodiments, system 100 may also determine whether a metric orother indication satisfies particular storage criteria sufficient toperform an action. For example, a storage policy or other definitionmight indicate that a storage manager 140 should initiate a particularaction if a storage metric or other indication drops below or otherwisefails to satisfy specified criteria such as a threshold of dataprotection. In some embodiments, risk factors may be quantified intocertain measurable service or risk levels. For example, certainapplications and associated data may be considered to be more importantrelative to other data and services. Financial compliance data, forexample, may be of greater importance than marketing materials, etc.Network administrators may assign priority values or “weights” tocertain data and/or applications corresponding to the relativeimportance. The level of compliance of secondary copy operationsspecified for these applications may also be assigned a certain value.Thus, the health, impact, and overall importance of a service may bedetermined, such as by measuring the compliance value and calculatingthe product of the priority value and the compliance value to determinethe “service level” and comparing it to certain operational thresholdsto determine whether it is acceptable. Further examples of the servicelevel determination are provided in U.S. Pat. No. 7,343,453, which isincorporated by reference herein.

System 100 may additionally calculate data costing and data availabilityassociated with information management operation cells. For instance,data received from a cell may be used in conjunction withhardware-related information and other information about system elementsto determine the cost of storage and/or the availability of particulardata. Exemplary information generated could include how fast aparticular department is using up available storage space, how long datawould take to recover over a particular pathway from a particularsecondary storage device, costs over time, etc. Moreover, in someembodiments, such information may be used to determine or predict theoverall cost associated with the storage of certain information. Thecost associated with hosting a certain application may be based, atleast in part, on the type of media on which the data resides, forexample. Storage devices may be assigned to a particular costcategories, for example. Further examples of costing techniques aredescribed in U.S. Pat. No. 7,343,453.

Any of the above types of information (e.g., information related totrending, predictions, job, cell or component status, risk, servicelevel, costing, etc.) can generally be provided to users via userinterface 158 in a single integrated view or console (not shown). Reporttypes may include: scheduling, event management, media management anddata aging. Available reports may also include backup history, dataaging history, auxiliary copy history, job history, library and drive,media in library, restore history, and storage policy, etc., withoutlimitation. Such reports may be specified and created at a certain pointin time as a system analysis, forecasting, or provisioning tool.Integrated reports may also be generated that illustrate storage andperformance metrics, risks and storage costing information. Moreover,users may create their own reports based on specific needs. Userinterface 158 can include an option to show a “virtual view” of thesystem that graphically depicts the various components in the systemusing appropriate icons. As one example, user interface 158 may providea graphical depiction of primary storage devices 104, secondary storagedevices 108, data agents 142 and/or media agents 144, and theirrelationship to one another in system 100.

In general, the operations management functionality of system 100 canfacilitate planning and decision-making. For example, in someembodiments, a user may view the status of some or all jobs as well asthe status of each component of information management system 100. Usersmay then plan and make decisions based on this data. For instance, auser may view high-level information regarding secondary copy operationsfor system 100, such as job status, component status, resource status(e.g., communication pathways, etc.), and other information. The usermay also drill down or use other means to obtain more detailedinformation regarding a particular component, job, or the like. Furtherexamples are provided in U.S. Pat. No. 7,343,453.

Information management system 100 can also be configured to performsystem-wide e-discovery operations in some embodiments. In general,e-discovery operations provide a unified collection and searchcapability for data in the system, such as data stored in secondarystorage devices 108 (e.g., backups, archives, or other secondary copies116). For example, system 100 may construct and maintain a virtualrepository for data stored in system 100 that is integrated acrosssource applications 110, different storage device types, etc. Accordingto some embodiments, e-discovery utilizes other techniques describedherein, such as data classification and/or content indexing.

Information Management Policies

An information management policy 148 can include a data structure orother information source that specifies a set of parameters (e.g.,criteria and rules) associated with secondary copy and/or otherinformation management operations.

One type of information management policy 148 is a “storage policy.”According to certain embodiments, a storage policy generally comprises adata structure or other information source that defines (or includesinformation sufficient to determine) a set of preferences or othercriteria for performing information management operations. Storagepolicies can include one or more of the following: (1) what data will beassociated with the storage policy, e.g., subclient; (2) a destinationto which the data will be stored; (3) datapath information specifyinghow the data will be communicated to the destination; (4) the type ofsecondary copy operation to be performed; and (5) retention informationspecifying how long the data will be retained at the destination (see,e.g., FIG. 1E). Data associated with a storage policy can be logicallyorganized into subclients, which may represent primary data 112 and/orsecondary copies 116. A subclient may represent static or dynamicassociations of portions of a data volume. Subclients may representmutually exclusive portions. Thus, in certain embodiments, a portion ofdata may be given a label and the association is stored as a staticentity in an index, database or other storage location. Subclients mayalso be used as an effective administrative scheme of organizing dataaccording to data type, department within the enterprise, storagepreferences, or the like. Depending on the configuration, subclients cancorrespond to files, folders, virtual machines, databases, etc. In oneexemplary scenario, an administrator may find it preferable to separatee-mail data from financial data using two different subclients.

A storage policy can define where data is stored by specifying a targetor destination storage device (or group of storage devices). Forinstance, where the secondary storage device 108 includes a group ofdisk libraries, the storage policy may specify a particular disk libraryfor storing the subclients associated with the policy. As anotherexample, where the secondary storage devices 108 include one or moretape libraries, the storage policy may specify a particular tape libraryfor storing the subclients associated with the storage policy, and mayalso specify a drive pool and a tape pool defining a group of tapedrives and a group of tapes, respectively, for use in storing thesubclient data. While information in the storage policy can bestatically assigned in some cases, some or all of the information in thestorage policy can also be dynamically determined based on criteria,which can be set forth in the storage policy. For instance, based onsuch criteria, a particular destination storage device(s) or otherparameter of the storage policy may be determined based oncharacteristics associated with the data involved in a particularsecondary copy operation, device availability (e.g., availability of asecondary storage device 108 or a media agent 144), network status andconditions (e.g., identified bottlenecks), user credentials, and thelike.

Datapath information can also be included in the storage policy. Forinstance, the storage policy may specify network pathways and componentsto utilize when moving the data to the destination storage device(s). Insome embodiments, the storage policy specifies one or more media agents144 for conveying data associated with the storage policy between thesource and destination. A storage policy can also specify the type(s) ofoperations associated with the storage policy, such as a backup,archive, snapshot, auxiliary copy, or the like. Furthermore, retentionparameters can specify how long the resulting secondary copies 116 willbe kept (e.g., a number of days, months, years, etc.), perhaps dependingon organizational needs and/or compliance criteria.

Another type of information management policy 148 is a “schedulingpolicy,” which specifies when and how often to perform operations.Scheduling parameters may specify with what frequency (e.g., hourly,weekly, daily, event-based, etc.) or under what triggering conditionssecondary copy or other information management operations are to takeplace. Scheduling policies in some cases are associated with particularcomponents, such as a subclient, client computing device 102, and thelike.

When adding a new client computing device 102, administrators canmanually configure information management policies 148 and/or othersettings, e.g., via user interface 158. However, this can be an involvedprocess resulting in delays, and it may be desirable to begin dataprotection operations quickly, without awaiting human intervention.Thus, in some embodiments, system 100 automatically applies a defaultconfiguration to client computing device 102. As one example, when oneor more data agent(s) 142 are installed on a client computing device102, the installation script may register the client computing device102 with storage manager 140, which in turn applies the defaultconfiguration to the new client computing device 102. In this manner,data protection operations can begin substantially immediately. Thedefault configuration can include a default storage policy, for example,and can specify any appropriate information sufficient to begin dataprotection operations. This can include a type of data protectionoperation, scheduling information, a target secondary storage device108, data path information (e.g., a particular media agent 144), and thelike.

Another type of information management policy 148 is an “audit policy”(or security policy), which comprises preferences, rules and/or criteriathat protect sensitive data in information management system 100. Forexample, an audit policy may define “sensitive objects” which are filesor data objects that contain particular keywords (e.g., “confidential,”or “privileged”) and/or are associated with particular keywords (e.g.,in metadata) or particular flags (e.g., in metadata identifying adocument or email as personal, confidential, etc.). An audit policy mayfurther specify rules for handling sensitive objects. As an example, anaudit policy may require that a reviewer approve the transfer of anysensitive objects to a cloud storage site, and that if approval isdenied for a particular sensitive object, the sensitive object should betransferred to a local primary storage device 104 instead. To facilitatethis approval, the audit policy may further specify how a secondarystorage computing device 106 or other system component should notify areviewer that a sensitive object is slated for transfer.

Another type of information management policy 148 is a “provisioningpolicy,” which can include preferences, priorities, rules, and/orcriteria that specify how client computing devices 102 (or groupsthereof) may utilize system resources, such as available storage oncloud storage and/or network bandwidth. A provisioning policy specifies,for example, data quotas for particular client computing devices 102(e.g., a number of gigabytes that can be stored monthly, quarterly orannually). Storage manager 140 or other components may enforce theprovisioning policy. For instance, media agents 144 may enforce thepolicy when transferring data to secondary storage devices 108. If aclient computing device 102 exceeds a quota, a budget for the clientcomputing device 102 (or associated department) may be adjustedaccordingly or an alert may trigger.

While the above types of information management policies 148 have beendescribed as separate policies, one or more of these can be generallycombined into a single information management policy 148. For instance,a storage policy may also include or otherwise be associated with one ormore scheduling, audit, or provisioning policies or operationalparameters thereof. Moreover, while storage policies are typicallyassociated with moving and storing data, other policies may beassociated with other types of information management operations. Thefollowing is a non-exhaustive list of items that information managementpolicies 148 may specify:

schedules or other timing information, e.g., specifying when and/or howoften to perform information management operations;

the type of secondary copy 116 and/or copy format (e.g., snapshot,backup, archive, HSM, etc.);

a location or a class or quality of storage for storing secondary copies116 (e.g., one or more particular secondary storage devices 108);

preferences regarding whether and how to encrypt, compress, deduplicate,or otherwise modify or transform secondary copies 116;

which system components and/or network pathways (e.g., preferred mediaagents 144) should be used to perform secondary storage operations;

resource allocation among different computing devices or other systemcomponents used in performing information management operations (e.g.,bandwidth allocation, available storage capacity, etc.);

whether and how to synchronize or otherwise distribute files or otherdata objects across multiple computing devices or hosted services; and

retention information specifying the length of time primary data 112and/or secondary copies 116 should be retained, e.g., in a particularclass or tier of storage devices, or within the system 100.

Information management policies 148 can additionally specify or dependon historical or current criteria that may be used to determine whichrules to apply to a particular data object, system component, orinformation management operation, such as:

frequency with which primary data 112 or a secondary copy 116 of a dataobject or metadata has been or is predicted to be used, accessed, ormodified;

time-related factors (e.g., aging information such as time since thecreation or modification of a data object);

deduplication information (e.g., hashes, data blocks, deduplicationblock size, deduplication efficiency or other metrics);

an estimated or historic usage or cost associated with differentcomponents (e.g., with secondary storage devices 108);

the identity of users, applications 110, client computing devices 102and/or other computing devices that created, accessed, modified, orotherwise utilized primary data 112 or secondary copies 116;

a relative sensitivity (e.g., confidentiality, importance) of a dataobject, e.g., as determined by its content and/or metadata;

the current or historical storage capacity of various storage devices;

the current or historical network capacity of network pathwaysconnecting various components within the storage operation cell;

access control lists or other security information; and

the content of a particular data object (e.g., its textual content) orof metadata associated with the data object.

Exemplary Storage Policy and Secondary Copy Operations

FIG. 1E includes a data flow diagram depicting performance of secondarycopy operations by an embodiment of information management system 100,according to an exemplary storage policy 148A. System 100 includes astorage manager 140, a client computing device 102 having a file systemdata agent 142A and an email data agent 142B operating thereon, aprimary storage device 104, two media agents 144A, 144B, and twosecondary storage devices 108: a disk library 108A and a tape library108B. As shown, primary storage device 104 includes primary data 112A,which is associated with a logical grouping of data associated with afile system (“file system subclient”), and primary data 112B, which is alogical grouping of data associated with email (“email subclient”). Thetechniques described with respect to FIG. 1E can be utilized inconjunction with data that is otherwise organized as well.

As indicated by the dashed box, the second media agent 144B and tapelibrary 108B are “off-site,” and may be remotely located from the othercomponents in system 100 (e.g., in a different city, office building,etc.). Indeed, “off-site” may refer to a magnetic tape located in remotestorage, which must be manually retrieved and loaded into a tape driveto be read. In this manner, information stored on the tape library 108Bmay provide protection in the event of a disaster or other failure atthe main site(s) where data is stored.

The file system subclient 112A in certain embodiments generallycomprises information generated by the file system and/or operatingsystem of client computing device 102, and can include, for example,file system data (e.g., regular files, file tables, mount points, etc.),operating system data (e.g., registries, event logs, etc.), and thelike. The e-mail subclient 112B can include data generated by an e-mailapplication operating on client computing device 102, e.g., mailboxinformation, folder information, emails, attachments, associateddatabase information, and the like. As described above, the subclientscan be logical containers, and the data included in the correspondingprimary data 112A and 112B may or may not be stored contiguously.

The exemplary storage policy 148A includes backup copy preferences (orrule set) 160, disaster recovery copy preferences or rule set 162, andcompliance copy preferences or rule set 164. Backup copy rule set 160specifies that it is associated with file system subclient 166 and emailsubclient 168. Each of subclients 166 and 168 are associated with theparticular client computing device 102. Backup copy rule set 160 furtherspecifies that the backup operation will be written to disk library 108Aand designates a particular media agent 144A to convey the data to disklibrary 108A. Finally, backup copy rule set 160 specifies that backupcopies created according to rule set 160 are scheduled to be generatedhourly and are to be retained for 30 days. In some other embodiments,scheduling information is not included in storage policy 148A and isinstead specified by a separate scheduling policy.

Disaster recovery copy rule set 162 is associated with the same twosubclients 166 and 168. However, disaster recovery copy rule set 162 isassociated with tape library 108B, unlike backup copy rule set 160.Moreover, disaster recovery copy rule set 162 specifies that a differentmedia agent, namely 144B, will convey data to tape library 108B.Disaster recovery copies created according to rule set 162 will beretained for 60 days and will be generated daily. Disaster recoverycopies generated according to disaster recovery copy rule set 162 canprovide protection in the event of a disaster or other catastrophic dataloss that would affect the backup copy 116A maintained on disk library108A.

Compliance copy rule set 164 is only associated with the email subclient168, and not the file system subclient 166. Compliance copies generatedaccording to compliance copy rule set 164 will therefore not includeprimary data 112A from the file system subclient 166. For instance, theorganization may be under an obligation to store and maintain copies ofemail data for a particular period of time (e.g., 10 years) to complywith state or federal regulations, while similar regulations do notapply to file system data. Compliance copy rule set 164 is associatedwith the same tape library 108B and media agent 144B as disasterrecovery copy rule set 162, although a different storage device or mediaagent could be used in other embodiments. Finally, compliance copy ruleset 164 specifies that copies generated under compliance copy rule set164 will be retained for 10 years and will be generated quarterly.

Secondary Copy Jobs

A logical grouping of secondary copy operations governed by a rule setand being initiated at a point in time may be referred to as a“secondary copy job” and sometimes may be called a “backup job,” eventhough it is not necessarily limited to creating backup copies.Secondary copy jobs may be initiated on demand as well. Steps 1-9 belowillustrate three secondary copy jobs based on storage policy 148A.

At step 1, storage manager 140 initiates a backup job according to thebackup copy rule set 160, which logically comprises all the secondarycopy operations necessary to effectuate rules 160 in storage policy 148Aevery hour, including steps 1-4 occurring hourly. For instance, ascheduling service running on storage manager 140 accesses backup copyrule set 160 or a separate scheduling policy associated with clientcomputing device 102 and initiates a backup job on an hourly basis.Thus, at the scheduled time, storage manager 140 sends instructions toclient computing device 102 (i.e., to both data agent 142A and dataagent 142B) to begin the backup job.

At step 2, file system data agent 142A and email data agent 142Boperating on client computing device 102 respond to the instructionsreceived from storage manager 140 by accessing and processing therespective subclient primary data 112A and 112B involved in the backupcopy operation, which can be found in primary storage device 104.Because the secondary copy operation is a backup copy operation, thedata agent(s) 142A, 142B may format the data into a backup format orotherwise process the data suitable for a backup copy.

At step 3, client computing device 102 (e.g., using file system dataagent 142A) communicates the processed data to the first media agent144A according to backup copy rule set 160, as directed by storagemanager 140. Storage manager 140 may further keep a record in managementdatabase 146 of the association between media agent 144A and one or moreof: client computing device 102, file system data agent 142A, and/orbackup copy 116A.

The target media agent 144A receives the data-agent-processed data fromclient computing device 102, and at step 4 generates and conveys backupcopy 116A to disk library 108A to be stored as backup copy 116A, againat the direction of storage manager 140 and according to backup copyrule set 160. Media agent 144A can also update its index 153 to includedata and/or metadata related to backup copy 116A, such as informationindicating where the backup copy 116A resides on disk library 108A, dataand metadata for cache retrieval, etc. Storage manager 140 may similarlyupdate its index 150 to include information relating to the secondarycopy operation, such as information relating to the type of operation, aphysical location associated with one or more copies created by theoperation, the time the operation was performed, status informationrelating to the operation, the components involved in the operation, andthe like. In some cases, storage manager 140 may update its index 150 toinclude some or all of the information stored in index 153 of mediaagent 144A. At this point, the backup job may be considered complete.After the 30-day retention period expires, storage manager 140 instructsmedia agent 144A to delete backup copy 116A from disk library 108A andindexes 150 and/or 153 are updated accordingly.

At step 5, storage manager 140 initiates another backup job according tothe disaster recovery rule set 162. Illustratively this includes steps5-7 occurring daily for creating disaster recovery copy 116B. Disasterrecovery copy 116B will be based on backup copy 116A and not on primarydata 112A and 112B.

At step 6, illustratively based on instructions received from storagemanager 140 at step 5, the specified media agent 144B retrieves the mostrecent backup copy 116A from disk library 108A.

At step 7, again at the direction of storage manager 140 and asspecified in disaster recovery copy rule set 162, media agent 144B usesthe retrieved data to create a disaster recovery copy 116B and store itto tape library 108B. In some cases, disaster recovery copy 1166 is adirect, mirror copy of backup copy 116A, and remains in the backupformat. In other embodiments, disaster recovery copy 1166 may begenerated in some other manner, such as by using primary data 112A, 112Bfrom primary storage device 104 as source data. The disaster recoverycopy operation is initiated once a day and disaster recovery copies 116Bare deleted after 60 days; indexes 153 and/or 150 are updatedaccordingly when/after each information management operation is executedand/or completed. The present backup job may be considered to becomplete.

At step 8, storage manager 140 initiates another backup job according tocompliance rule set 164, which includes steps 8-9 occurring quarterlyfor creating compliance copy 116C. For instance, storage manager 140instructs media agent 144B to create compliance copy 116C on tapelibrary 108B, as specified in the compliance copy rule set 164.

At step 9 in the example, compliance copy 116C is generated usingdisaster recovery copy 116B as the source. In other embodiments,compliance copy 116C is instead generated using primary data 112Bcorresponding to the email subclient or using backup copy 116A from disklibrary 108A as source data. As specified in the illustrated example,compliance copies 116C are created quarterly, and are deleted after tenyears, and indexes 153 and/or 150 are kept up-to-date accordingly.

Exemplary Applications of Storage Policies—Information GovernancePolicies and Classification

Storage manager 140 may permit a user to specify aspects of storagepolicy 148A. For example, the storage policy can be modified to includeinformation governance policies to define how data should be managed inorder to comply with a certain regulation or business objective. Thevarious policies may be stored, for example, in management database 146.An information governance policy may align with one or more compliancetasks that are imposed by regulations or business requirements. Examplesof information governance policies might include a Sarbanes-Oxleypolicy, a HIPAA policy, an electronic discovery (e-discovery) policy,and so on.

Information governance policies allow administrators to obtain differentperspectives on an organization's online and offline data, without theneed for a dedicated data silo created solely for each differentviewpoint. As described previously, the data storage systems hereinbuild an index that reflects the contents of a distributed data set thatspans numerous clients and storage devices, including both primary dataand secondary copies, and online and offline copies. An organization mayapply multiple information governance policies in a top-down manner overthat unified data set and indexing schema in order to view andmanipulate the data set through different lenses, each of which isadapted to a particular compliance or business goal. Thus, for example,by applying an e-discovery policy and a Sarbanes-Oxley policy, twodifferent groups of users in an organization can conduct two verydifferent analyses of the same underlying physical set of data/copies,which may be distributed throughout the information management system.

An information governance policy may comprise a classification policy,which defines a taxonomy of classification terms or tags relevant to acompliance task and/or business objective. A classification policy mayalso associate a defined tag with a classification rule. Aclassification rule defines a particular combination of criteria, suchas users who have created, accessed or modified a document or dataobject; file or application types; content or metadata keywords; clientsor storage locations; dates of data creation and/or access; reviewstatus or other status within a workflow (e.g., reviewed orun-reviewed); modification times or types of modifications; and/or anyother data attributes in any combination, without limitation. Aclassification rule may also be defined using other classification tagsin the taxonomy. The various criteria used to define a classificationrule may be combined in any suitable fashion, for example, via Booleanoperators, to define a complex classification rule. As an example, ane-discovery classification policy might define a classification tag“privileged” that is associated with documents or data objects that (1)were created or modified by legal department staff, or (2) were sent toor received from outside counsel via email, or (3) contain one of thefollowing keywords: “privileged” or “attorney” or “counsel”, or otherlike terms. Accordingly, all these documents or data objects will beclassified as “privileged.”

One specific type of classification tag, which may be added to an indexat the time of indexing, is an “entity tag.” An entity tag may be, forexample, any content that matches a defined data mask format. Examplesof entity tags might include, e.g., social security numbers (e.g., anynumerical content matching the formatting mask XXX-XX-XXXX), credit cardnumbers (e.g., content having a 13-16 digit string of numbers), SKUnumbers, product numbers, etc. A user may define a classification policyby indicating criteria, parameters or descriptors of the policy via agraphical user interface, such as a form or page with fields to befilled in, pull-down menus or entries allowing one or more of severaloptions to be selected, buttons, sliders, hypertext links or other knownuser interface tools for receiving user input, etc. For example, a usermay define certain entity tags, such as a particular product number orproject ID code that is relevant in the organization. In someimplementations, the classification policy can be implemented usingcloud-based techniques. For example, the storage devices may be cloudstorage devices, and the storage manager 140 may execute cloud serviceprovider API over a network to classify data stored on cloud storagedevices.

Restore Operations from Secondary Copies

While not shown in FIG. 1E, at some later point in time, a restoreoperation can be initiated involving one or more of secondary copies116A, 1166, 116C. A restore operation logically takes a selectedsecondary copy 116, reverses the effects of the secondary copy operationthat created it, and stores the restored data to primary storage where aclient computing device 102 may properly access it as primary data. Amedia agent 144 and an appropriate data agent 142 (e.g., executing onthe client computing device 102) perform the tasks needed to complete arestore operation. For example, data that was encrypted, compressed,and/or deduplicated in the creation of secondary copy 116 will becorrespondingly rehydrated (reversing deduplication), uncompressed, andunencrypted into a format appropriate to primary data. In general,restored data should be indistinguishable from other primary data 112.Preferably, the restored data has fully regained the native format thatmay make it immediately usable by application 110.

As one example, a user may manually initiate a restore of backup copy116A, e.g., by interacting with user interface 158 of storage manager140 or with a web-based console with access to system 100. Storagemanager 140 may accesses data in its index 150 and/or managementdatabase 146 (and/or the respective storage policy 148A) associated withthe selected backup copy 116A to identify the appropriate media agent144A and/or secondary storage device 108A where the secondary copyresides. The user may be presented with a representation (e.g., stub,thumbnail, listing, etc.) and metadata about the selected secondarycopy, in order to determine whether this is the appropriate copy to berestored, e.g., date that the original primary data was created. Storagemanager 140 will then instruct media agent 144A and an appropriate dataagent 142 to restore secondary copy 116A to primary storage device 104.A media agent may be selected for use in the restore operation based ona load balancing algorithm, an availability based algorithm, or othercriteria. The selected media agent, e.g., 144A, retrieves secondary copy116A from disk library 108A. For instance, media agent 144A may accessits index 153 to identify a location of backup copy 116A on disk library108A, or may access location information residing on disk library 108Aitself.

In some cases when backup copy 116A was recently created or accessed,caching may speed up the restore operation. In such a case, media agent144A accesses a cached version of backup copy 116A residing in index153, without having to access disk library 108A for some or all of thedata. Once it has retrieved backup copy 116A, the media agent 144Acommunicates the data to the requesting client computing device 102.Upon receipt, file system data agent 142A and email data agent 142B mayunpackage (e.g., restore from a backup format to the native applicationformat) the data in backup copy 116A and restore the unpackaged data toprimary storage device 104. In general, secondary copies 116 may berestored to the same volume or folder in primary storage device 104 fromwhich the secondary copy was derived; to another storage location orclient computing device 102; to shared storage. In some cases the datamay be restored so that it may be used by an application 110 of adifferent version/vintage from the application that created the originalprimary data 112.

Exemplary Secondary Copy Formatting

The formatting and structure of secondary copies 116 can vary dependingon the embodiment. In some cases, secondary copies 116 are formatted asa series of logical data units or “chunks” (e.g., 512 MB, 1 GB, 2 GB, 4GB, or 8 GB chunks). This can facilitate efficient communication andwriting to secondary storage devices 108, e.g., according to resourceavailability. For example, a single secondary copy 116 may be written ona chunk-by-chunk basis to one or more secondary storage devices 108. Insome cases, users can select different chunk sizes, e.g., to improvethroughput to tape storage devices. Generally, each chunk can include aheader and a payload. The payload can include files (or other dataunits) or subsets thereof included in the chunk, whereas the chunkheader generally includes metadata relating to the chunk, some or all ofwhich may be derived from the payload. For example, during a secondarycopy operation, media agent 144, storage manager 140, or other componentmay divide files into chunks and generate headers for each chunk byprocessing the files. The headers can include a variety of informationsuch as file identifier(s), volume(s), offset(s), or other informationassociated with the payload data items, a chunk sequence number, etc.Importantly, in addition to being stored with secondary copy 116 onsecondary storage device 108, the chunk headers can also be stored toindex 153 of the associated media agent(s) 144 and/or to index 150associated with storage manager 140. This can be useful in some casesfor providing faster processing of secondary copies 116 during browsing,restores, or other operations. In some cases, once a chunk issuccessfully transferred to a secondary storage device 108, thesecondary storage device 108 returns an indication of receipt, e.g., tomedia agent 144 and/or storage manager 140, which may update theirrespective indexes 153, 150 accordingly. During restore, chunks may beprocessed (e.g., by media agent 144) according to the information in thechunk header to reassemble the files.

Data can also be communicated within system 100 in data channels thatconnect client computing devices 102 to secondary storage devices 108.These data channels can be referred to as “data streams”, and multipledata streams can be employed to parallelize an information managementoperation, improving data transfer rate, among other advantages. Exampledata formatting techniques including techniques involving datastreaming, chunking, and the use of other data structures in creatingsecondary copies are described in U.S. Pat. Nos. 7,315,923 8,156,086,and 8,578,120.

FIGS. 1F and 1G are diagrams of example data streams 170 and 171,respectively, which may be employed for performing informationmanagement operations. Referring to FIG. 1F, data agent 142 forms datastream 170 from source data associated with a client computing device102 (e.g., primary data 112). Data stream 170 is composed of multiplepairs of stream header 172 and stream data (or stream payload) 174. Datastreams 170 and 171 shown in the illustrated example are for asingle-instanced storage operation, and a stream payload 174 thereforemay include both single-instance (SI) data and/or non-SI data. A streamheader 172 includes metadata about the stream payload 174. This metadatamay include, for example, a length of the stream payload 174, anindication of whether the stream payload 174 is encrypted, an indicationof whether the stream payload 174 is compressed, an archive fileidentifier (ID), an indication of whether the stream payload 174 issingle instanceable, and an indication of whether the stream payload 174is a start of a block of data.

Referring to FIG. 1G, data stream 171 has the stream header 172 andstream payload 174 aligned into multiple data blocks. In this example,the data blocks are of size 64 KB. The first two stream header 172 andstream payload 174 pairs comprise a first data block of size 64 KB. Thefirst stream header 172 indicates that the length of the succeedingstream payload 174 is 63 KB and that it is the start of a data block.The next stream header 172 indicates that the succeeding stream payload174 has a length of 1 KB and that it is not the start of a new datablock. Immediately following stream payload 174 is a pair comprising anidentifier header 176 and identifier data 178. The identifier header 176includes an indication that the succeeding identifier data 178 includesthe identifier for the immediately previous data block. The identifierdata 178 includes the identifier that the data agent 142 generated forthe data block. The data stream 171 also includes other stream header172 and stream payload 174 pairs, which may be for SI data and/or non-SIdata.

FIG. 1H is a diagram illustrating data structures 180 that may be usedto store blocks of SI data and non-SI data on a storage device (e.g.,secondary storage device 108). According to certain embodiments, datastructures 180 do not form part of a native file system of the storagedevice. Data structures 180 include one or more volume folders 182, oneor more chunk folders 184/185 within the volume folder 182, and multiplefiles within chunk folder 184. Each chunk folder 184/185 includes ametadata file 186/187, a metadata index file 188/189, one or morecontainer files 190/191/193, and a container index file 192/194.Metadata file 186/187 stores non-SI data blocks as well as links to SIdata blocks stored in container files. Metadata index file 188/189stores an index to the data in the metadata file 186/187. Containerfiles 190/191/193 store SI data blocks. Container index file 192/194stores an index to container files 190/191/193. Among other things,container index file 192/194 stores an indication of whether acorresponding block in a container file 190/191/193 is referred to by alink in a metadata file 186/187. For example, data block B2 in thecontainer file 190 is referred to by a link in metadata file 187 inchunk folder 185. Accordingly, the corresponding index entry incontainer index file 192 indicates that data block B2 in container file190 is referred to. As another example, data block B1 in container file191 is referred to by a link in metadata file 187, and so thecorresponding index entry in container index file 192 indicates thatthis data block is referred to.

As an example, data structures 180 illustrated in FIG. 1H may have beencreated as a result of separate secondary copy operations involving twoclient computing devices 102. For example, a first secondary copyoperation on a first client computing device 102 could result in thecreation of the first chunk folder 184, and a second secondary copyoperation on a second client computing device 102 could result in thecreation of the second chunk folder 185. Container files 190/191 in thefirst chunk folder 184 would contain the blocks of SI data of the firstclient computing device 102. If the two client computing devices 102have substantially similar data, the second secondary copy operation onthe data of the second client computing device 102 would result in mediaagent 144 storing primarily links to the data blocks of the first clientcomputing device 102 that are already stored in the container files190/191. Accordingly, while a first secondary copy operation may resultin storing nearly all of the data subject to the operation, subsequentsecondary storage operations involving similar data may result insubstantial data storage space savings, because links to already storeddata blocks can be stored instead of additional instances of datablocks.

If the operating system of the secondary storage computing device 106 onwhich media agent 144 operates supports sparse files, then when mediaagent 144 creates container files 190/191/193, it can create them assparse files. A sparse file is a type of file that may include emptyspace (e.g., a sparse file may have real data within it, such as at thebeginning of the file and/or at the end of the file, but may also haveempty space in it that is not storing actual data, such as a contiguousrange of bytes all having a value of zero). Having container files190/191/193 be sparse files allows media agent 144 to free up space incontainer files 190/191/193 when blocks of data in container files190/191/193 no longer need to be stored on the storage devices. In someexamples, media agent 144 creates a new container file 190/191/193 whena container file 190/191/193 either includes 100 blocks of data or whenthe size of the container file 190 exceeds 50 MB. In other examples,media agent 144 creates a new container file 190/191/193 when acontainer file 190/191/193 satisfies other criteria (e.g., it containsfrom approximately 100 to approximately 1000 blocks or when its sizeexceeds approximately 50 MB to 1 GB). In some cases, a file on which asecondary copy operation is performed may comprise a large number ofdata blocks. For example, a 100 MB file may comprise 400 data blocks ofsize 256 KB. If such a file is to be stored, its data blocks may spanmore than one container file, or even more than one chunk folder. Asanother example, a database file of 20 GB may comprise over 40,000 datablocks of size 512 KB. If such a database file is to be stored, its datablocks will likely span multiple container files, multiple chunkfolders, and potentially multiple volume folders. Restoring such filesmay require accessing multiple container files, chunk folders, and/orvolume folders to obtain the requisite data blocks.

Examples of Migrating Data Between Magnetic Disks in Magnetic Storage

As described herein, the systems and methods facilitate the migration ofdata volumes stored on magnetic disks within magnetic disk storage, suchas by facilitating the transfer of data volumes contained in mount pathsprovided by the magnetic disk storage from existing magnetic disks toother disks or other data storage media. For example, the migration isto new magnetic disks during running secondary copy (e.g., backup)operations that are utilizing the magnetic disk storage to transfer orstore data from computing devices to the magnetic disk storage.

FIG. 2 is a block diagram illustrating devices for transferring datafrom a computing device to magnetic disk storage. As described herein,the media agent 144 manages, coordinates, and facilitates thetransmission of data, as directed by the storage manager 140, between aclient computing device 102 and one or more secondary storage devices108, such as magnetic disks 220. In general, the media agent 144generally provides a portal to the secondary storage devices 108, andmay generate and store information relating to characteristics of thestored data and/or metadata, as well as generate and store other typesof information that generally provides insight into the contents of thesecondary storage devices 108.

The secondary storage device 108 includes a virtual magnetic library210, which represents various mount paths 215, such as MOUNTPATH_1,MOUNTPATH_2, and MOUNTPATH_3, as depicted in the Figure. As describedherein, the virtual magnetic library 210 is a virtual library associatedwith the mount paths 215, through which data is sent, copied,transferred, or otherwise streamed to magnetic media 220 within thesecondary storage 108.

The magnetic media 220 may include individual hard magnetic disks,groups of disks, and/or RAID arrays, which are logically divided intopartitions 225, that include some or all of the total magnetic diskstorage space available to store data volumes. A partition 225 of amagnetic disk may include or be associated with a mount path 215, orfile system path, through which data is written from the media agent 144to the magnetic disk 220 and read from the magnetic disk 220 by themedia agent 144. For example, partition PART_1 may be associated withmount path MOUNTPATH_1, PART_2 may be associated with mount pathMOUNTPATH_2, PART_3 may be associated with mount path MOUNTPATH_3, andso on.

In some embodiments, the mount paths 215 contain volume folders (e.g.,V_1, V_2, . . . , V_volumeID), which are utilized by data streams whenperforming copy jobs during running secondary copy operations. Forexample, a unique data stream, or job, utilizes a unique volume folder,contained by a mount path 215. During running secondary copy operations,target folders may be marked as “open” (denoting that they are activefolders accepting copy jobs from the media agent 144), “full” (denotingthat they are non-active folders not accepting copy jobs from the mediaagent 144) and/or “remove” (denoting that they can be removed due to anaging policy or other retention policies).

The marking of a folder, for example as “full” or “open” may be adatabase operation performed within the virtual magnetic library 210 todenote whether new data (e.g., new copy jobs) should be directed to thefolder. Such a marking may reflect that a volume folder, and the mountpath it represents, is at capacity, has been utilized for a certainperiod of time (e.g., 8 hours of a backup operation), and so on.

The media agent 144 may stream jobs to the mount paths 215 duringrunning secondary copy operations in a variety of ways. For example, themedia agent 144 may follow a “fill and spill” policy, wherein the mediaagent 144 completely fills a disk space of a first mount path based on aspace allocation established for the first mount path 215, beforewriting to another mount path. The fill and spill policy facilitates theconsolidation of data onto the magnetic media 220, withoutfragmentation.

As another example, the media agent 144 may instead follow a “spill andfill” policy, where the media agent 144 writes to the mount paths 215 inparallel. The spill and fill policy facilitates maximum throughput,especially when there are several mount paths 215, although data may befragmented between the available mount paths 215.

As described herein, in some embodiments, the information managementsystem 100, via the media agent 144, may facilitate the migration froman existing magnetic disk to a new magnetic disk while secondary copyoperations are running and transferring data via the media agent 144 tothe secondary storage device 108. The systems and methods, therefore,may provide a disk migration system 200, which provides variouscomponents and performs various methods or operations to orchestratesuch disk migration (or, the refreshing of the mount paths 215represented by the virtual magnetic library 210). For example, the diskmigration system 200 enables, facilitates, and/or manages the migrationof stored backed up data to other magnetic disks without interrupting orotherwise affecting running secondary copy operations that are stillactively writing to the original magnetic disks.

FIG. 3 is a block diagram illustrating the components of the diskmigration system 200. The disk migration system 200 may include one ormore modules and/or components to refresh the mount paths 215represented by the virtual magnetic library 210 of magnetic secondarystorage 108. The modules and/or components may be hardware, software, ora combination of hardware and software, and may be executed by one ormore processors (e.g., such as secondary storage computing device 106,which hosts and executes media agent 144). For example, the diskmigration system 200 may include an access component 310, a migrationcomponent 320, and a temporary mount path component 330.

In some embodiments, the access component 310 is configured and/orprogrammed to access or receive a request to migrate data volumes storedon an existing magnetic disk to a new magnetic disk. Often, the accesscomponent 310 will access or receive the request to migrate data betweenexisting and new magnetic disks while secondary copy operations arecurrently running to transfer data to the magnetic library.

In some cases, an administrator or customer may submit a request to theinformation management system 100 to change some or all existingmagnetic disks to new magnetic disks for magnetic secondary storagedevices 108. In other cases, the information management system 100(e.g., the storage manager 140) may automatically generate a request torefresh the mount paths 215 of the secondary storage device 100 after acertain time period of use, after receiving an indication of wear orother use-based issues, and so on.

In some embodiments, the migration component 320 migrates, or causes tomigrate, data volumes from the existing magnetic disks to the newmagnetic disks. At the time of migration (e.g., at or soon after therequest is accessed or received), the migration component 320 maymigrate some or all full, or non-active, data volumes.

For all active mount paths associated with currently running secondarycopy operations transferring data to the existing magnetic disk, themigration component 320 marks each mount path as full when a runningsecondary copy operation associated with the mount path has completed ajob to transfer data to the existing magnetic disk. For example, themigration component 320, upon completion of a copy job for a mount path215, marks (e.g., performs a database operation within the virtualmagnetic library 210) the mount path folder associated with the mountpath 215 as full, regardless of whether the mount path 215 is actuallyfull or slated to be non-active. The migration component 320 may thenmigrate data volumes associated with the newly marked (e.g., from “open”to “full”) mount paths to the new magnetic disk.

Once the migration of data volumes is complete, the migration component320 may mark all mount paths 215 migrated to the new magnetic disk asopen, which provides the secondary copy operations with access to themount paths 215 to copy data to the new magnetic disk.

In some embodiments, the migration component 320 may assist in directingrunning secondary copy operations to a new magnetic disk. For example,the migration component 320 may determine an expected time period tomigrate the data volumes associated with the non-active mount paths tothe new magnetic disk (e.g., an expected time period based on an amountof data to migrate and/or based on a current operational status ofvarious components utilized during the copying of the data volumes tothe new magnetic disk).

Then, for some or all of the active mount paths associated with thecurrently running secondary copy operations, the migration component 320marks the mount paths as full, as described herein, when the predictedtime period lapses, and migrates the data volumes associated with themount paths marked as full to the new magnetic disk.

In some embodiments, the disk migration system 200 utilizes thetemporary mount path component 330 to direct running secondary copyoperations (such as backup copy operations, archive copy operations,reference copy operations, CDR copy operations, and so on) to the newmagnetic disk. For example, the temporary mount path component 330creates one or more temporary mount paths on the new magnetic disk forall the active mount paths associated with the currently runningsecondary copy operations.

The temporary mount path component 330 may then direct all jobsperformed by the running secondary copy operations to the createdtemporary mount paths during migration of data volumes associated withmount paths marked as non-active to the new magnetic disk. When writingdata to the temporary mount paths, the disk migration system 200 may,using links within the chunks of the copied data, insert references thatrelate the temporary mount path to an associated mount path currentlymarked as full and under migration to the new magnetic disk. Thus, thetemporary mount path may act, in some cases, as the same volume folderto which data volumes contained by the “full’ mount path are beingtransferred/copied/migrated.

Once the mount paths marked as non-active are marked as open on the newmagnetic disk, the temporary mount path component 330 causes all jobsperformed by the running secondary copy operations to be redirected tothe mouth paths marked as open on the new magnetic disk (the originalmount paths). Thus, the temporary mount path component 330 redirects therunning secondary copy operations back to the original mount paths,after the data volumes have been fully migrated between magnetic disks.

Thus, the disk migration system 200 performs various operations torefresh the mount paths (e.g., migrate data volumes between magneticdisks) within magnetic secondary storage. FIG. 4 depicts a method 400for migrating data from an existing magnetic disk to a new magnetic diskwithin magnetic storage. The method 400 may be performed by the diskmigration system 200 and, accordingly, is described herein merely by wayof reference thereto. It will be appreciated that the method 400 may beperformed on any suitable hardware or devices/components within theinformation management system 100.

In operation 410, the disk migration system 200 accesses a request toreplace an existing magnetic disk storing one or more data volumes andassociated with one or more mount paths with a new magnetic disk. Forexample, an administrator or customer may submit a request to theinformation management system 100 to change some or all existingmagnetic disks to new magnetic disks for magnetic secondary storagedevices 108 used to store data during secondary copy operations. Inother cases, the information management system 100 may automaticallygenerate a request to refresh the mount paths 215 of the secondarystorage device 100 after a certain time period of use, after receivingan indication of wear or other use-based issues, and so on.

In operation 420, when the request is accessed while secondary copyoperations associated with the one or more mount paths are currentlyrunning to transfer data to one or more partitions of the existingmagnetic disk that are mapped to the one or more mount paths of themagnetic disk library, the disk migration system 200, for all non-activemount paths, migrates, at a first time, data volumes associated with thenon-active mount paths to the new magnetic disk.

In parallel, in operation 430, the disk migration system 200, marks eachmount path as non-active when a running secondary copy operationassociated with the mount path has completed a job, for all active mountpaths associated with the currently running secondary copy operations.

For example, the migration component 320, upon completion of a copy jobfor a mount path 215, marks (e.g., performs database operation withinthe virtual magnetic library 210) the mount path folder associated withthe mount path 215 as full, regardless of whether the mount path 215 isactually full or slated to be non-active.

In operation 440, the disk migration system 200 migrates, at a secondtime later than the first time, data volumes associated with the mountpath marked as non-active to the new magnetic disk. For example, themigration component 320 migrates data volumes associated with the newlymarked (e.g., from “open” to “full”) mount paths to the new magneticdisk.

In operation 450, the disk migration system 200, for all mount pathsmigrated to the new magnetic disk, marks each mount path as resident onthe new magnetic disk. For example, the migration component 320 may marksome or all previously active mount paths 215 migrated to the newmagnetic disk as open, which provides the secondary copy operations withaccess to the mount paths 215 to transfer data to the new magnetic disk.

As described herein, in some embodiments, the disk migration system 200,via the migration component 320, may assist in directing runningsecondary copy operations to a new magnetic disk. For example, themigration component 320 may determine an expected time period to migratethe data volumes associated with the non-active mount paths to the newmagnetic disk (e.g., an expected time period based on an amount of datato migrate and/or based on a current operational status of variouscomponents utilized during the copying of the data volumes to the newmagnetic disk).

However, in some embodiments, the disk migration system 200 may providethe running secondary copy operations with access to the new magneticdisk while the data volumes are being migrated from the existingmagnetic disk to the new magnetic disk. FIG. 5 depicts a method 500 fortransferring data to magnetic storage during a magnetic disk migration.The method 500 may be performed by the disk migration system 200 and,accordingly, is described herein merely by way of reference thereto. Itwill be appreciated that the method 500 may be performed on any suitablehardware or devices/components within the information management system100.

In operation 510, the data migration system 200, e.g., via the temporarymount path component 330, creates one or more temporary mount paths onthe new magnetic disk for all the active mount paths associated with thecurrently running secondary copy operations.

In operation 520, the data migration system 200 sends all jobs performedby the running secondary copy operations to the created temporary mountpaths during migration of data volumes associated with mount pathsmarked as non-active to the new magnetic disk.

In operation 530, when the mount paths marked as non-active are markedas resident on the new magnetic disk, the data migration system 200, inoperation 540, returns or redirects all jobs performed by the runningsecondary copy operations to the mouth paths marked as resident on thenew magnetic disk.

In some embodiments, the data migration system 200 may utilizeinformation associated with a current or expected capacity of targetmount paths when redirecting secondary copy jobs to mount paths. Forexample, when a first mount path is close to full, and a second mountpath has available space for new data, the data migration system 200 mayperform the various operations described herein to migrate data from thefull, or low capacity mount path to the mount path having the availablecapacity.

Thus, in some embodiments, the data migration system 200 performs amount path refresh, change, and/or update of a magnetic library withoutinterrupting running secondary copy operations copying data to magneticstorage. FIGS. 6A-6C are block diagrams illustrating the implementationof magnetic disk migration in magnetic disk storage.

FIG. 6A depicts the virtual magnetic library 210 at a first timeassociated with receiving an initial request to refresh the mount paths215 of the magnetic library 210. At the first time, the media agent 144is directing running secondary copy operations to transfer data toMOUNTPATH_3, which has an associated volume folder 617 marked as open,while no running secondary copy operations are copying data toMOUTHPATH_1 or MOUNTPATH_2, which have volume folders 613 and 615 markedas full. As described in method 300, the disk migration system 200, atthe first time, causes data volumes associated with MOUTHPATH_1 andMOUNTPATH_2 to be copied to new partitions 625 (e.g., NEWPART_1 andNEWPART_2) of a new magnetic disk 610.

FIG. 6B depicts the virtual magnetic library 210 at a second timeassociated with completion of all remaining copy jobs at MOUNTPATH_3. Atthe second time, the disk migration system 200, according to method 300,marks the volume folder 617 associated with MOUNTPATH_3 as full, andcauses the data volume associated with MOUNTPATH_3 to be copied to thenew partition 625 (NEWPART_3). In addition, the disk migration system200 creates a temporary mount path 630 (MOUNTPATH_TEMP_3) that isassociated with MOUNTPATH_3, and, according to method 500, causes themedia agent 144 to direct the running secondary copy operations to thetemporary mount path 630.

FIG. 6C depicts the virtual magnetic library 210 at a third timeassociated with completion of the migration of all data volumes to thenew magnetic disk 610. Once migration is complete (and the mount paths215 are refreshed), the disk migration system 200, according to method500, marks the volume folders 613, 615, 617 to open, and causes themedia agent 144 to direct the running secondary copy operations to theopen, and now active, mount paths (e.g., MOUNTPATH_1, MOUNTPATH_2, andMOUNTPATH_3).

Thus, in some embodiments, the disk migration system 200 facilitates therefreshing of mount paths of magnetic storage during running secondarycopy operations to the magnetic storage, by streaming, from the mediaagent 144, data to one or more data volumes contained in one or morepartitions of a first magnetic disk of the magnetic library. The diskmigration system 200 marks each of the one or more mount paths as fullwhen a running secondary copy operation associated with the mount pathhas completed a job (regardless of the actual current capacity orintended use of the mount path), and migrates each of the one or moredata volumes to a second magnetic disk of the magnetic library when themount path associated with the data volume is marked as full.

EXAMPLE EMBODIMENTS

In some embodiments, the systems and methods described herein refreshmount paths of a magnetic library by accessing a request to replace anexisting magnetic disk storing one or more data volumes and associatedwith one or more mount paths with a new magnetic disk, wherein therequest is accessed while secondary copy operations associated with theone or more mount paths are currently running to transfer data to one ormore partitions of the existing magnetic disk that are mapped to the oneor more mount paths of the magnetic disk library. Further, for allnon-active mount paths, the systems and methods migrate, at a firsttime, data volumes associated with the non-active mount paths to the newmagnetic disk, and for all active mount paths associated with thecurrently running secondary copy operations, mark each mount path asnon-active when a running secondary copy operation associated with themount path has completed a job, and migrate, at a second time later thanthe first time, data volumes associated with the mount path marked asnon-active to the new magnetic disk. Once migration is complete, for allmount paths migrated to the new magnetic disk, the systems and methodsmark each mount path as resident on the new magnetic disk.

Further, the systems and methods may create one or more temporary mountpaths on the new magnetic disk for all the active mount paths associatedwith the currently running secondary copy operations, send all jobsperformed by the running secondary copy operations to the createdtemporary mount paths during migration of data volumes associated withmount paths marked as non-active to the new magnetic disk, and when themount paths marked as non-active are marked as resident on the newmagnetic disk, return all jobs performed by the running secondary copyoperations to the mouth paths marked as resident on the new magneticdisk.

In some embodiments, the systems and methods access, via an accesscomponent, a request to migrate data volumes stored on an existingmagnetic disk to a new magnetic disk, wherein the request is accessedwhile secondary copy operations are currently running to transfer datato the existing magnetic disk, and for all active mount paths associatedwith the currently running secondary copy operations transferring datato the existing magnetic disk, mark, via a migration component, eachmount path as full when a running secondary copy operation associatedwith the mount path has completed a job to copy data to the existingmagnetic disk, and migrate, via the migration component, data volumesassociated with the mount path marked as full to the new magnetic disk.

In some embodiments, the systems and methods cause a media agent toperform a secondary copy operation of data to magnetic disks of amagnetic library by streaming, via the media agent, data to one or moredata volumes contained in one or more partitions of a first magneticdisk of the magnetic library, wherein the one or more partitions areassociated with one or more mount paths through which data istransferred to the one or more data volumes stored by the one or morepartitions of the first magnetic disk, marking each of the one or moremount paths as full when a running secondary copy operation associatedwith the mount path has completed a job, and migrating each of the oneor more data volumes to a second magnetic disk of the magnetic librarywhen the mount path associated with the data volume is marked as full.

TERMINOLOGY

Conditional language, such as, among others, “can,” “could,” “might,” or“may,” unless specifically stated otherwise, or otherwise understoodwithin the context as used, is generally intended to convey that certainembodiments include, while other embodiments do not include, certainfeatures, elements and/or steps. Thus, such conditional language is notgenerally intended to imply that features, elements and/or steps are inany way required for one or more embodiments or that one or moreembodiments necessarily include logic for deciding, with or without userinput or prompting, whether these features, elements and/or steps areincluded or are to be performed in any particular embodiment.

Unless the context clearly requires otherwise, throughout thedescription and the claims, the words “comprise,” “comprising,” and thelike are to be construed in an inclusive sense, as opposed to anexclusive or exhaustive sense; that is to say, in the sense of“including, but not limited to.” As used herein, the terms “connected,”“coupled,” or any variant thereof means any connection or coupling,either direct or indirect, between two or more elements; the coupling orconnection between the elements can be physical, logical, or acombination thereof. Additionally, the words “herein,” “above,” “below,”and words of similar import, when used in this application, refer tothis application as a whole and not to any particular portions of thisapplication. Where the context permits, words in the above DetailedDescription using the singular or plural number may also include theplural or singular number respectively. The word “or” in reference to alist of two or more items, covers all of the following interpretationsof the word: any one of the items in the list, all of the items in thelist, and any combination of the items in the list. Likewise the term“and/or” in reference to a list of two or more items, covers all of thefollowing interpretations of the word: any one of the items in the list,all of the items in the list, and any combination of the items in thelist.

Depending on the embodiment, certain operations, acts, events, orfunctions of any of the algorithms described herein can be performed ina different sequence, can be added, merged, or left out altogether(e.g., not all are necessary for the practice of the algorithms).Moreover, in certain embodiments, operations, acts, functions, or eventscan be performed concurrently, e.g., through multi-threaded processing,interrupt processing, or multiple processors or processor cores or onother parallel architectures, rather than sequentially.

Systems and modules described herein may comprise software, firmware,hardware, or any combination(s) of software, firmware, or hardwaresuitable for the purposes described herein. Software and other modulesmay reside and execute on servers, workstations, personal computers,computerized tablets, PDAs, and other computing devices suitable for thepurposes described herein. Software and other modules may be accessiblevia local memory, via a network, via a browser, or via other meanssuitable for the purposes described herein. Data structures describedherein may comprise computer files, variables, programming arrays,programming structures, or any electronic information storage schemes ormethods, or any combinations thereof, suitable for the purposesdescribed herein. User interface elements described herein may compriseelements from graphical user interfaces, interactive voice response,command line interfaces, and other suitable interfaces.

Further, the processing of the various components of the illustratedsystems can be distributed across multiple machines, networks, and othercomputing resources. In addition, two or more components of a system canbe combined into fewer components. Various components of the illustratedsystems can be implemented in one or more virtual machines, rather thanin dedicated computer hardware systems and/or computing devices.Likewise, the data repositories shown can represent physical and/orlogical data storage, including, for example, storage area networks orother distributed storage systems. Moreover, in some embodiments theconnections between the components shown represent possible paths ofdata flow, rather than actual connections between hardware. While someexamples of possible connections are shown, any of the subset of thecomponents shown can communicate with any other subset of components invarious implementations.

Embodiments are also described above with reference to flow chartillustrations and/or block diagrams of methods, apparatus (systems) andcomputer program products. Each block of the flow chart illustrationsand/or block diagrams, and combinations of blocks in the flow chartillustrations and/or block diagrams, may be implemented by computerprogram instructions. Such instructions may be provided to a processorof a general purpose computer, special purpose computer,specially-equipped computer (e.g., comprising a high-performancedatabase server, a graphics subsystem, etc.) or other programmable dataprocessing apparatus to produce a machine, such that the instructions,which execute via the processor(s) of the computer or other programmabledata processing apparatus, create means for implementing the actsspecified in the flow chart and/or block diagram block or blocks.

These computer program instructions may also be stored in anon-transitory computer-readable memory that can direct a computer orother programmable data processing apparatus to operate in a particularmanner, such that the instructions stored in the computer-readablememory produce an article of manufacture including instruction meanswhich implement the acts specified in the flow chart and/or blockdiagram block or blocks. The computer program instructions may also beloaded onto a computing device or other programmable data processingapparatus to cause a series of operations to be performed on thecomputing device or other programmable apparatus to produce a computerimplemented process such that the instructions which execute on thecomputer or other programmable apparatus provide steps for implementingthe acts specified in the flow chart and/or block diagram block orblocks.

Any patents and applications and other references noted above, includingany that may be listed in accompanying filing papers, are incorporatedherein by reference. Aspects of the invention can be modified, ifnecessary, to employ the systems, functions, and concepts of the variousreferences described above to provide yet further implementations of theinvention.

These and other changes can be made to the invention in light of theabove Detailed Description. While the above description describescertain examples of the invention, and describes the best modecontemplated, no matter how detailed the above appears in text, theinvention can be practiced in many ways. Details of the system may varyconsiderably in its specific implementation, while still beingencompassed by the invention disclosed herein. As noted above,particular terminology used when describing certain features or aspectsof the invention should not be taken to imply that the terminology isbeing redefined herein to be restricted to any specific characteristics,features, or aspects of the invention with which that terminology isassociated. In general, the terms used in the following claims shouldnot be construed to limit the invention to the specific examplesdisclosed in the specification, unless the above Detailed Descriptionsection explicitly defines such terms. Accordingly, the actual scope ofthe invention encompasses not only the disclosed examples, but also allequivalent ways of practicing or implementing the invention under theclaims.

To reduce the number of claims, certain aspects of the invention arepresented below in certain claim forms, but the applicant contemplatesthe various aspects of the invention in any number of claim forms. Forexample, while only one aspect of the invention is recited as ameans-plus-function claim under 35 U.S.C sec. 112(f) (AIA), otheraspects may likewise be embodied as a means-plus-function claim, or inother forms, such as being embodied in a computer-readable medium. Anyclaims intended to be treated under 35 U.S.C. § 112(f) will begin withthe words “means for”, but use of the term “for” in any other context isnot intended to invoke treatment under 35 U.S.C. § 112(f). Accordingly,the applicant reserves the right to pursue additional claims afterfiling this application, in either this application or in a continuingapplication.

What is claimed is:
 1. A method, performed by an information management system, for refreshing mount paths of a data storage library, the method comprising: identifying a request to replace an existing disk associated with one or more mount paths with a new disk, wherein one or more partitions are mapped to the one or more mount paths of the data storage library; for all non-active mount paths, migrating, at a first time, data associated with the non-active mount paths to the new disk; for all active mount paths: marking each mount path as non-active when a running operation associated with the mount path has completed a job; and migrating, at a second time later than the first time, data associated with the mount path marked as non-active to the new disk; and for all mount paths migrated to the new disk, marking each mount path as resident on the new disk.
 2. The method of claim 1, further comprising: creating one or more temporary mount paths on the new disk for all active mount paths associated with currently running operations; sending all jobs performed by the running operations to the created temporary mount paths; and when the mount paths marked as non-active are marked as resident on the new disk, returning all jobs performed by the running operations to the mount paths marked as resident on the new disk.
 3. The method of claim 1, further comprising: predicting a time period, commencing with the first time to migrate the data associated with the non-active mount paths to the new disk; and for all the active mount paths associated with currently running operations: marking the mount paths as non-active when the predicted time period lapses; and migrating the data associated with the mount paths marked as non-active to the new disk.
 4. The method of claim 1, wherein the data storage library is a virtual storage library that represents a list of mount paths through which data is transferred from a media agent to disks.
 5. The method of claim 1, wherein each of the one or more mount paths represented by the data storage library contain volume folders associated with data stored to disks via the one or more mount paths.
 6. The method of claim 1, wherein a media agent performs operations using a fill and spill mount path allocation policy or a spill and fill mount path allocation policy.
 7. The method of claim 1, wherein the existing disk is a magnetic disk or an optical disk.
 8. The method of claim 1, wherein marking each mount path of the active mount paths as non-active when a running operation associated with the mount path has completed a job includes marking a non-full mount path as full when the running operation completes a currently running copy job.
 9. The method of claim 1, wherein marking each mount path of the active mount paths as non-active when a running operation associated with the mount path has completed a job includes performing a database operation within the data storage library to indicate a mount path cannot perform another job associated with running operations.
 10. The method of claim 1, wherein marking each mount path of the active mount paths as non-active when a running operation associated with the mount path has completed a job includes marking each mount path as full until data associated with the mount path marked as full have completed a migration to the new disk.
 11. A system, comprising: at least one processor; at least one data storage device coupled to the at least one processor and storing instructions for implementing a process to migrate data between disks, wherein the process comprises: accessing a request to migrate data stored on an existing disk to a new disk; for all active mount paths associated with running operations, marking, via a migration component, each mount path as full when a running operation associated with the mount path has completed a job to transfer data to the existing disk; and migrating, via the migration component, data associated with the mount path marked as full to the new disk.
 12. The system of claim 11, wherein the migration component marks all mount paths migrated to the new disk as open to receive data to transfer to the new disk.
 13. The system of claim 11, wherein the migration component migrates data associated with non-active mount paths to the new disk before migrating the data associated with the active mount paths to the new disk.
 14. The system of claim 11, wherein the migration component migrates data associated with non-active mount paths to the new disk before marking the active mount paths as full.
 15. The system of claim 11, wherein the process further comprises: creating, via a temporary mount path component, one or more temporary mount paths on the new disk for all the active mount paths associated with the running operations; directing all jobs performed by the running operations to the created temporary mount paths during migration of data associated with mount paths marked as non-active to the new disk; and when the mount paths marked as non-active are marked as open on the new disk, redirecting, all jobs performed by the running operations to the mount paths marked as open on the new disk.
 16. The system of claim 11, wherein the migration component is further configured to: predict a time period to migrate the data associated with the non-active mount paths to the new disk; and for all the active mount paths associated with the currently running operations: mark the mount paths as full when the predicted time period lapses; and migrate the data associated with the mount paths marked as full to the new disk.
 17. The system of claim 11, wherein the access component and the migration component are part of a media agent within an information management system that is configured to perform the currently running operations.
 18. The system of claim 11, wherein each of the one or more mount paths are represented by a virtual magnetic library containing volume folders associated with data stored to disks via the one or more mount paths.
 19. A computer-readable medium, excluding transitory propagating signals, storing instructions that, when executed by an information management system, cause the information management system to perform transfer of data to disks of a data storage library, the method comprising: transferring data to one or more data contained in one or more partitions of a first disk of the data storage library, wherein the one or more partitions are associated with one or more mount paths through which data is transferred to the one or more data stored by the one or more partitions of the first disk; marking each of the one or more mount paths as full when a running operation associated with the mount path has completed a job; and transferring each of the one or more data to another data storage medium after the mount path associated with the data is marked as full.
 20. The computer-readable medium of claim 19, wherein the other data storage medium is a second disk, and wherein the method further comprises: creating one or more temporary mount paths to the second disk; directing jobs performed by the running operations to the created temporary mount paths during migration of the one or more data to the second disk; and when the migration of the one or more data to the second disk is complete, redirecting the jobs performed by the running operations to the mount paths. 